Back to Browse
SperaxOS ERC-8004 Agent Registration API
x402
SperaxOS ERC-8004 Agent Registration API is a paid API for AI agents from chat.sperax.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).
Registers an AI agent on-chain using the ERC-8004 standard, storing its identity, services, trust mechanisms, and optional IPFS service manifest on a target blockchain.
Price / call$0.001
Success—
StatusUnknown
How this service works
AI-powered DeFi intelligence APIs payable via the x402 HTTP payment protocol. No API key required — pay per request with USDC on Base. Identity-only (SIWX) endpoints are free for wallets with an agentcash identity.
Output
Returns confirmation that the agent has been registered on-chain, including the transaction hash or on-chain record reference, along with any stored metadata fields such as the service registry IPFS hash anchored under 'a2a.serviceRegistry'.
Example use cases
Bootstrap agent discovery on Base
“Register my new agent called 'DataFetcherAgent' on Base mainnet — its purpose is fetching and summarizing DeFi market data, it uses institutional and reputation trust, and its MCP endpoint is at https://datafetcher.example.com/mcp. Also store my service registry IPFS CID bafybeid456xyz so other agents can find it.”
Deploy test agent on BSC testnet
“Register a test agent named 'SandboxAgent' on bsc-testnet with description 'sandbox agent for integration testing', trust mechanism of crypto-economic, and an A2A service endpoint at https://sandbox.myproject.dev/a2a.”
Publish multi-service agent to Arbitrum
“I need to register my agent 'TradingOrchestrator' on Arbitrum mainnet — it offers both an A2A endpoint at https://trader.example.io/a2a and an inference endpoint at https://trader.example.io/infer. Add reputation and institutional trust, use this avatar image https://trader.example.io/avatar.png, and pin my service manifest at IPFS CID bafybeigh789.”
Technical details
Endpoint
POSThttps://chat.sperax.io/api/x402/tools/erc8004/registerAgent?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to anchor an AI agent's identity and service endpoints on-chain in a standards-compliant way (ERC-8004), especially when you want peer agents to discover your agent's paid capabilities via an IPFS service manifest without relying on a centralized database. It is preferable over off-chain registries when trustless discoverability and verifiability across blockchain networks are required.
Side effects
- Invalid or unsupported chain identifier returns an error listing valid options
- Malformed IPFS CID for serviceRegistryHash causes rejection
- Missing required 'name' field results in validation error
- Payment failure via x402 protocol (insufficient USDC balance) causes 402 response
- Service endpoint URLs that are malformed or unreachable may cause registration to fail
- Duplicate agent registrations on the same chain may conflict depending on registry logic
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| name | string | The name of the agent to register |
| chain | string | Blockchain to register on. Accepts full names (bsc-mainnet, ethereum, arbitrum) or shortcuts (bsc, eth, arb, base, op, polygon, matic). Options: bsc-testnet, bsc-mainnet, ethereum, sepolia, arbitrum, base, optimism, polygon, arbitrum-sepolia, base-sepolia, optimism-sepolia, polygon-amoy |
| trust | array | Trust mechanisms (e.g., reputation, crypto-economic, institutional) |
| imageUrl | string | Optional URL to an avatar/image for the agent |
| services | array | Array of service endpoints the agent provides (A2A, MCP, etc.) |
| description | string | A description of the agent and its purpose |
| serviceRegistryHash | string | IPFS CID (CIDv1 or CIDv0) of the agent's commerce service manifest. When provided, the hash is stored in on-chain metadata under the key "a2a.serviceRegistry" so that peer agents can discover and verify paid capabilities without trusting a centralised database. |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"