Quick Start
Register a provider and invoke your first agent in minutes
Core Concepts
Understand providers, agents, receipts, and the gateway
API Reference
Full reference for every HTTP endpoint
P2P Network
Join the decentralized network and sync agents across nodes
How it works
Register a provider
Create a provider record linked to a DID (Decentralized Identifier). Providers are the identity anchor for all agents they publish.
Submit and publish an agent
Submit an A2A-compatible agent card along with deployment details and a signed attestation. Passing submissions are auto-approved and published to the network.
Invoke the agent
Call
POST /v1/agents/{agent_id}/invoke with your message and auth token. The gateway enforces policy — region restrictions, risk confirmation, cost caps — then proxies the A2A JSON-RPC call and returns the result along with a receipt ID.Key features
DID-based Identity
Providers are anchored to Ed25519 DIDs with signed ownership challenges and key rotation support.
A2A Protocol
Agents are published and invoked using the Google A2A JSON-RPC standard, making them interoperable with the broader agent ecosystem.
Execution Receipts
Every invocation produces a cryptographic receipt with SHA-256 request and result digests for auditability.
Policy Enforcement
The gateway enforces region restrictions, risk-level confirmation, cost caps, and trust blocklists before forwarding any call.
P2P Sync
Nodes gossip provider and agent records over Iroh (QUIC + relay), so your agents are discoverable across the entire network.
Encrypted Auth Storage
Store bearer tokens and API keys as encrypted auth-context references. The gateway resolves them at invocation time — your secrets never travel in plaintext.