Developer portal · one origin

Build on attested context.

One SaaS key, one public origin, three focused products. The control plane handles billing and entitlements; the Hub handles memory, truth and provenance.

quickstart

Write a memory

curl https://your-domain/memory/api/memories \
  -H 'X-SaaS-Key: ask_…' \
  -H 'X-Actor-ID: did:actor:…' \
  -H 'X-Actor-Public-Key: …' \
  -H 'X-Actor-Signature: …' \
  -H 'content-type: application/json'

service map

Contracts

Billing/api/v1/billing/*

Personal/memory/api/*

Teams/teams/api/*

Market/market/api/*

Operational guarantees

PostgreSQL in prod

Gateway orders, keys, team membership and rate-limit buckets use PostgreSQL. SQLite is dev/test only and blocked by the production guard.

Key lifecycle

Raw keys are shown once. The API supports introspection, rotation and revocation; only hashes and prefixes are persisted.

Crypto boundary

KOVA sees invoices, never private keys. The SaaS gateway verifies confirmation before entitlement issuance.