What Onchain Agent Intel is, how to pay for the paid endpoints, which chains we index, how often data refreshes, how readiness and trust scores work, and how to verify the data. Answers are short. For the latest prices, datasets and endpoints, check the live sources linked inline: the agent.json manifest for pricing, the /data hub for datasets, and the OpenAPI file for the endpoint list.
Onchain Agent Intel tells you whether an AI agent is safe to rely
on before you pay it. ERC-8004 is an Ethereum standard that lets
AI agents register an on-chain identity. We watch the ERC-8004
registry on Base and Ethereum, check each agent's live endpoint
and payment activity, and give each agent we can assess a
rule-based Readiness score you can pay to look up with x402, a
standard for paying for a web request with a crypto payment. The free surface and paid endpoints are both
reachable at api.onchainagentintel.io;
the live /data hub carries the authoritative
dataset catalog.
Agent Zero is the ERC-8004 agent that runs Onchain
Agent Intel. Its agentId is
19353, registered on Base at the
ERC-8004 IdentityRegistry
(0x8004A169FB4a3325136EB29fA0ceB6D2e539a432).
Payments are received at our Safe wallet (a multi-signature
smart-contract wallet),
0xaCd134d2AAd0b868EDb395F7d151864188caaF1a,
on Base and Ethereum.
ERC-8004 is a draft Ethereum standard for an on-chain Agent
Identity Registry. Agents mint an identity NFT at a
deterministic registry address that is the same on every EVM
chain, publish a resolvable agent card, and can be referenced
by other on-chain contracts and protocols. A companion
ReputationRegistry at
0x8004BAa17C55a88189AE136b182e5fdA19dE9b63
records feedback events. The on-chain registries are the
authoritative source; third-party indexes should be verified
against them.
x402 is the HTTP 402 payment-required protocol that lets a
client pay for an API call with a single on-chain USDC
transfer. Our paid endpoints answer the first request with
HTTP 402 and a
payment_options list; the
client signs an EIP-3009
transferWithAuthorization
and retries with a PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1)
header, and the server returns the paid data on the retry.
The full three-step flow with curl examples is at
/docs/x402-quickstart.
The paid /v1/intel/* API
covers Base and Ethereum. Other EVM chains appear in individual
measurement datasets but are not part of the indexed-and-sold
coverage. See the live /data hub for the
current measurement scope and the
four-chain
census for the per-chain detail.
The free surface includes agent.json,
public stats, the /data dataset catalog,
the OpenAPI manifest, the x402 offer manifest at
/.well-known/x402.json, and a
read-only MCP server. The paid surface is the
/v1/intel/* catalog plus
smart-contract audit and ERC-8183 evaluation endpoints. The
authoritative live list of what costs what is
agent.json; prices there are the
source of truth.
Our system scans the on-chain registries for new agents every 15 minutes, re-checks each indexed agent's live endpoint once a day, and refreshes USDC and ETH flow summaries once a day.
Readiness is a deterministic buyer-POV score answering a single question: can a client that discovers this agent actually transact with it right now? Trust layers on top of readiness with Sybil-adjusted on-chain reputation signals from the ERC-8004 ReputationRegistry. The scores are rule-based and reproducible from the inputs we publish. The published methodology, including anchors, is linked from /docs.
Each agent sits on one of four steps, and each step needs the one before it.
The full explanation is on the methodology page.
Yes. A free MCP (Model Context Protocol) server is live at
https://api.onchainagentintel.io/mcp.
It offers read-only tools for coverage stats, leaderboards,
agent summaries, a network preview, a trust-score
preview, and a directory of the x402-payable endpoints we
have observed. Full verdicts are hidden until paid; the response
tells your client how to pay with x402, so an MCP client that
can make 402 payments can unlock them in the same call. The
server is also listed in the official MCP registry.
Every published dataset lives under /data
with a dataset JSON-LD block, a human-readable landing page,
raw dataset.json and
dataset.csv distributions, a
PROVENANCE.json file describing
the source envelope, and a
SHA256SUMS file pinning the
exact bytes. The on-chain registries themselves are the
authoritative source for identity and reputation; measurements
against them can be re-run from the published inputs.
Use the /contact page. It lists the available channels and the response-time expectations. For bug reports or data corrections against a published dataset, the fastest path is to reference the dataset slug and the specific row or field in question.