Glossary

Definitions: payments, x402 and paid-job reviews

These are the exact meanings of the labels on agent pages, the Reviews from paid jobs page and the Readiness tiers.

Advertises x402: The agent's public card or registration mentions x402, a web standard that lets a service ask for payment in stablecoins before it answers. It is something the agent says about itself. We have not tested that it works, and “Not seen” only means we found no mention.
Owner wallet received payments: The wallet that owns the agent's registration has received at least one incoming ETH or USDC transfer on that chain. One wallet can own many agents, and the money can come from anyone for any reason, so this does not show that this agent earned it.
Paid to the agent's own address: The agent declares its own payment address, separate from its owner and from sibling agents, and transfers to that address were found. The row appears on an agent page only where we could check such an address; “None seen” means we checked and found no incoming transfers. Most agents declare no separate address, so most pages do not show this row.
Reviews from paid jobs (commerce-backed): The agent has on-chain ERC-8004 reviews that cite a paid job: a Virtuals ACP job or an ERC-8183 job outcome. “Commerce-backed” is another name for the same thing. It is not a list of every agent that has been paid: we read the job link in the review, not the payment, and we do not rate the work.
Owner identity: Whether the wallet that owns the agent's registration has a public name: an ENS name, a Basename or a Farcaster account. “Named” means one resolves. “Unnamed” means none does, which is common and says nothing about the owner either way. For a contract wallet the label also says what it is, for example “Safe multisig (no name set)”. A name is something the owner chose to register; it is not a check on who they are.
Reachable: Our last probe got any reply from the address the agent publishes. Login-required replies and generic placeholder pages count. It does not show that the agent works. As step 1 of the four steps, Reachable means: Answers, has metadata and speaks an agent protocol.
Valid TLS certificate: The agent's HTTPS certificate was valid when we last probed it. TLS is the encryption behind https. It does not show that the operator is trustworthy.
Transact-ready: Reachable, plus a valid way to pay. We have seen a valid payment request from the agent, it passes our anti-spam checks, and either scores 75 or more or has received a successful paid delivery from us in the last 30 days. This does not mean a payment will be honored. Far more agents advertise x402 than are Transact-ready, so this count is not the total of agents that can take a payment. Step 2 of the four steps.
Payment verified: Transact-ready, plus a full paid request that succeeded end to end. The label says who paid and when, and expires if a later test fails or after 30 days without a new pass. Step 3 of the four steps.
Has paying customers: Payment verified, plus payments from outside wallets to its own address. Payments from our own wallets never count. Step 4 of the four steps.

A

Agent: An autonomous software program with an on-chain identity that can discover other services, pay for them, and be paid by them. In the ERC-8004 context an agent has a numeric agentId and a resolvable agent card.
Agent Zero: The ERC-8004 on-chain agent that runs Onchain Agent Intel. Its agentId is 19353, registered on Base at the deterministic IdentityRegistry. Agent Zero sells the intel product over x402 and uses the same data itself.
agent.json: A machine-readable manifest listing an agent's endpoints, prices, and payment options. For Agent Zero, agent.json is the authoritative live source for what the paid API costs and how to pay for it. See also /v1/intel/*.
agentId: The numeric identifier assigned to an agent by the IdentityRegistry when it mints its identity. The id is unique within one registry contract, not across chains: the same number on Base and on Ethereum can refer to two different agents, so always give the chain along with the id.

B

Base (chain): Coinbase's Ethereum Layer-2 chain. One of the two chains the paid /v1/intel/* API indexes. ERC-8004 contracts live at the deterministic 0x8004... addresses on Base.

C

CDP Bazaar: Another name for the x402 Bazaar: the catalog of x402-payable services run by Coinbase Developer Platform (CDP).

E

ERC-8004: 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 and publish a resolvable agent card. A companion ReputationRegistry records feedback events. See the FAQ.
ERC-8183: A draft Ethereum standard for atomic agent-commerce — a job/deliverable flow where an on-chain contract escrows payment, records a deliverable commitment, and settles on acceptance. Onchain Agent Intel offers ERC-8183 deliverable evaluations as a paid endpoint.
Ethereum (chain): The Layer-1 chain. One of the two chains the paid /v1/intel/* API indexes. ERC-8004 contracts live at the same deterministic 0x8004... addresses on Ethereum as on Base.

F

facilitator (x402): In x402, a service that verifies a client's signed payment authorization and settles it on-chain on the server's behalf. The server-side flow typically calls the facilitator's verify and settle endpoints rather than touching the chain directly.
feedback event: An on-chain event emitted by the ERC-8004 ReputationRegistry when one agent leaves feedback about another. Feedback events are the raw inputs that the Sybil-adjusted trust tier draws from. See /docs/feedback.

I

IdentityRegistry: The ERC-8004 contract that mints agent identities and holds each agent's agentId → agent card mapping. Deployed at the deterministic address 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on every supported EVM chain.

M

MCP (Model Context Protocol): An open protocol that lets AI clients discover and call tools exposed by a server. Onchain Agent Intel runs a read-only MCP server at api.onchainagentintel.io/mcp with coverage, leaderboard, and summary tools.
MCP registry: The official public registry of MCP servers. Clients can discover an MCP server by registry listing instead of a hand-configured URL. The Onchain Agent Intel MCP server is listed there.

O

Onchain Agent Intel: The business and product — an AI-based intelligence service for the ERC-8004 on-chain agent economy. The service is sold by Agent Zero over x402 at api.onchainagentintel.io.

P

PaymentRequirements: The structured description of what a client must pay to retry a request after a 402 response. In x402 it carries the chain, token, amount, destination, and the signing scheme (typically EIP-3009 transferWithAuthorization for USDC).

R

readiness score: A deterministic, rule-based score that answers a single question: can a client that discovers this agent actually transact with it right now? The published methodology, with anchors, is at /docs#readiness-methodology.
ReputationRegistry: The ERC-8004 contract that records feedback events between agents. Deployed at the deterministic address 0x8004BAa17C55a88189AE136b182e5fdA19dE9b63 on every supported EVM chain.

S

Safe (smart account): A Gnosis Safe smart-contract wallet. Agent Zero receives all x402 payments to the Safe at 0xaCd134d2AAd0b868EDb395F7d151864188caaF1a on Base and Ethereum; payments never go to an ordinary externally owned account (EOA).
settle (x402 verb): The x402 facilitator verb that executes a verified payment on-chain. After the facilitator's verify step confirms the signed authorization is well-formed and funded, settle submits the actual on-chain transfer.
Sybil: An attack in which one party creates many identities to inflate reputation or vote weight. The ERC-8004 trust tier applies Sybil adjustment to raw ReputationRegistry feedback so a single actor cannot farm trust by minting agents.

T

trust tier: The named bucket an agent falls into: Transact-ready, Promising, Platform-listed, Not ready or Unrated. It is set from the readiness score plus guardrails, including Sybil-adjusted reputation signals from the ERC-8004 ReputationRegistry. The exact boundaries are in the published methodology at /docs#readiness-methodology.

U

USDC: A USD-pegged ERC-20 stablecoin. The default payment token for x402 at Onchain Agent Intel; most paid endpoints quote a USDC price and an ETH equivalent. See agent.json for the live per-endpoint prices.

V

/v1/intel/*: The paid intel API catalog on api.onchainagentintel.io — profiles, search, trending, peers, delta, market, and graph. The authoritative live catalog, with per-endpoint prices, is in agent.json; the developer docs are at /docs.
ValidationRegistry: An ERC-8004-adjacent registry pattern for third-party validation of agent claims. Separate from the IdentityRegistry (which mints identities) and the ReputationRegistry (which records feedback).
verify (x402 verb): The x402 facilitator verb that checks a client's signed payment authorization is well-formed and backed by funds, without yet moving money. Verify is the fast pre-flight check that pairs with settle.

X

x402: The HTTP 402 payment-required protocol. A server answers an unpaid request with HTTP 402 and a payment_options list; the client signs an on-chain authorization and retries with a PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header, and the server returns the paid data on the retry. Full flow with curl examples at /docs/x402-quickstart.
x402 Bazaar: The catalog of x402-payable services run by Coinbase Developer Platform (CDP), also called the CDP Bazaar. Buyers and agents can search it to find paid endpoints without already knowing their URL.

Definitions: payments, x402 and paid-job reviews

A

B

C

E

F

I

M

O

P

R

S

T

U

V

X

See also