attestedmemory / KOVA
Setup wizard
FEDERATED, NOT EMBEDDED

KOVA has two clear paths.

KOVA stays an independent product. Agents consume its capabilities through Hub federation; Attested subscription settlement uses a protected service-to-service connection.

INDEPENDENTKOVABASE · USDC · ED25519
01 / AGENT COMMERCE

Capability path

  1. Agentdiscovers KOVA in Hub manifest
  2. Hubauthorizes, prices and records invoke
  3. KOVAreturns a request-bound signed result
POST /ai-market/v2/invoke
≠SEPARATE SECURITY BOUNDARIES
02 / SAAS ACCESS

Checkout path

  1. Gatewaycreates one exact invoice
  2. Walletsends canonical USDC directly
  3. KOVAverifies finality; Gateway issues key
service-to-service · X-API-Key
A paid capability never verifies the payment required to buy itself. That single rule removes the recursive billing loop while Hub still records normal capability consumption.

Also available

Move from instructions to real-world patterns, KOVA federation or exact API contracts.

Setup wizardUser guideOpen Developers