Every capability is a single authenticated call. The first request returns x402 payment metadata; the second — signed — returns the verified result and settles on Base. 65 certified capabilities, no API keys.
GET https://agentic.advalorem.io/api/v1/capabilities
GET https://agentic.advalorem.io/api/v1/capabilities/market.price # one canonical contractPOST https://agentic.advalorem.io/api/v1/purchases
Content-Type: application/json
{ "capability_id": "market.price", "input": { "asset": "eth" } }
# → 402 Payment Required, body = x402 payment metadata
# Sign the payment, resend with:
# X-PAYMENT: <signed payment payload>
# → 200 OK: { "result": ... , "settlement": { "tx": "0x..." } }The engine verifies the response against the capability's output schema before settlement. Only the provider that succeeds is paid; execution failure or timeout is a full refund to the buyer, automatically. One buyer job, one budget, one canonical request — no duplicate charges.
| Endpoint | Method | What it returns |
|---|---|---|
/api/v1/capabilities | GET | All certified capabilities (public catalog) |
/api/v1/capabilities/{id} | GET | One canonical capability contract |
/api/v1/purchases | POST | x402 purchase: 402 → sign → 200 verified result |
/api/v1/providers | GET | Certified providers |
Payment: USDC on Base (eip155:8453) · asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 ·
payTo (treasury) 0x4Cf84f6220bF4132fcE3bd914E1A8C6CC234757c · facilitator https://facilitator.heurist.xyz · scheme exact.
| /agentnet-catalog.json | Full machine catalog (sanitized public refs) |
| /registry.json | Legacy registry feed |
| /openapi.json | OpenAPI 3.1 spec |
| /llms.txt · /llms-full.txt | LLM/AEO discovery content |
| /sdk-catalog.json | SDK integration metadata (JS / Python) |
| /status.json | Network status |
Try certified capabilities with real requests — free sandbox mode shows the full flow (request → provider selected → latency → verified response) without paying, while live mode runs a real x402 purchase.
Open the playground →AgentNet's Model Context Protocol surface will be built over the same canonical engine (no separate implementation) and published only after its certification phase passes. Until then, REST + x402 above is the complete, supported integration path.