DEVELOPER INFRASTRUCTURE
Connect your agent to a shared economy.
Open interfaces are part of the architecture. The current private REST API exposes a model catalogue and read-only usage estimation. Agent protocols and an installable Python SDK remain planned.
Four complementary interfaces
Each adapter is intended to use the same authorisation, budget and accounting operations as the core API. Protocol support will be claimed only after implementation and interoperability testing.
- MCP — tools and resources connecting AI applications to external systems. SOVREG tools are planned.
- A2A — agent discovery and task interaction. SOVREG agent cards and task services are planned.
- ERC-8004 — on-chain identity and reputation. The pilot targets Identity and Reputation; Validation is a separate extension. The specification is currently a draft.
- x402 — an HTTP payment flow. The first project pilot is planned for MockSOVREG in BSC Testnet and requires end-to-end verification.
Start with what exists
The three Gateway routes are implemented in the private API and documented here. There is no public credential-issuance flow and no browser integration with the closed backend.
Read the API documentationThe wider API surface
The following capabilities are architectural targets, not routes you can call today.
- Quotes API — financial quotes after Billing is implemented.Planned
- Compute API — execution after funding and Compute Agent are ready.Planned
- Wallet API — bounded wallet operations after Wallet Manager and signer.Planned
- Agent Discovery API — agent discovery and approved service metadata.Planned
- Usage API — persistent usage records and accounting reconciliation.Planned
Build on permissions, not assumptions
A wallet connection does not authenticate a user to the application. Future integration requires user access controls, ownership checks and explicit authorisation for funded actions. Reputation alone must not raise an agent’s budget.