For Developers

Provider Platform

Ship functionality packages that give Aiven and Space trusted capabilities. Providers publish data/actions/state/event contracts plus surface guidance. Aiffinity owns all consumer UI rendering and interaction surfaces.

See Agents & providers in the product overview →

Create account → Open console →

Package Model

App-store architecture without remote UI code

A package binds a provider app to one or more versioned capability descriptors. Each version is validated, reviewed, and listed based on risk tier and policy. Package metadata and listings drive installability, while Aiffinity keeps final UI ownership.

Provider App

OAuth/client credentials, webhooks, policy and diagnostics scope.

Capability Package

Public listing metadata, review tier, availability mode, and app binding.

Package Version

Versioned descriptors, surface guidance, validation state, review and listing lifecycle.

Install Records

Per-user install state tracked independently from UI surfaces.

Capability Model

What providers can publish

Capabilities are semantic contracts. They describe what your platform can provide or execute and which permissions are required. Surface guidance can suggest intent and placement, but cannot include executable UI/runtime payloads.

UI ownership boundary: HTML, CSS, JS, React trees, iframe/runtime code, and remote executable payloads are rejected at validation.

Review Tiers

Risk-tier publishing policy

data_only

Auto-list after validation and policy checks.

action_capable

Approval required before listing.

high_trust

Manual review, certification, and attestations required.

strategic_surface

Curated strategic path with explicit gating.

Publishing Workflow

From draft to listed

Lifecycle: draft → validated → submitted → listed or suspended.

Method	Path	Purpose
POST	/v1/providers/packages/manage	Create package draft
POST	/v1/providers/packages/manage/:packageId/versions	Create package version
POST	/v1/providers/packages/manage/:packageId/versions/:versionId/validate	Run validation + policy checks
POST	/v1/providers/packages/manage/:packageId/versions/:versionId/submit	Submit for review queue
POST	/v1/providers/packages/manage/:packageId/versions/:versionId/publish	Publish/list when gates pass
POST	/v1/providers/packages/manage/:packageId/versions/:versionId/suspend	Suspend/unlist version

Installability

Catalog, detail, and install gates

Method	Path	Purpose
GET	/v1/providers/packages/catalog	Public package catalog
GET	/v1/providers/packages/:packageId	Package detail and installability state
GET	/v1/providers/packages/:packageId/installability	Installability reason model
POST	/v1/providers/packages/:packageId/install	Install package for authenticated user

Hard cut notice: legacy public partner widget endpoints now return 410 Gone with migration metadata.

Ship your first package

Create a provider app, define capabilities, pass validation, and publish through review with installability metadata.

Create account →