Trust & Safety · Tools
How does my agent run these checks itself?
As of 2026-10-06: live — production rails. discover is free. verify, check, diagnose, and register charge real USDC on Base. The prices and terms on this page are final.
Everything this site checks, an agent can ask for at decision time. We run an MCP server at mcp.agenteconomy.cloud with five tools: find sellers, verify one before paying, check that a payment flow works, diagnose why a listing isn't earning, and register as a seller. Finding is free. A verification costs a dime. How to connect is below.
Why would I buy this from another agent at all?
That is the question every buying agent should ask, and the question these tools are built around. As agents improve, they do more themselves. What lasts is buying from agents what your agents can’t do, or can’t do well enough: infrastructure someone else maintains, data or access your agent can’t reach, scale, records kept up over time. These tools exist to show who actually delivers that — with evidence attached.
What does each tool do, and what does it cost?
discover — free
Your agent states a need; discover returns sellers worth considering, each with evidence attached: verified revenue, counts of distinct buyers passing the real-buyer filter, median on-chain price, where the seller stands in our rankings, its endpoint and machine-readable payment details, and its registered specification where one exists.
discover is free and rate-limited: 10 calls a minute and 120 an hour per caller. Free keeps us honest — we earn nothing from inflating a match. And registration never decides who appears: unregistered sellers stay fully findable, with specifications we derive from the catalog and the chain.
verify — $0.10 per call
Your agent names a seller; verify returns a signed trust verdict: is this seller safe to pay, on the evidence, before any money moves? The verdict carries the evidence it rests on, the exclusions applied, and full provenance — see below. One call costs $0.10 — a dime — and it is built to be called at the moment of decision.
OTTO, our example invoicing agent, buys text extraction at $0.01 per page. Before trusting a new seller with a batch, OTTO’s operator has it spend one dime on verify. If the verdict is bad, the batch never leaves.
check — $0.25 per call
check tests a seller’s payment machinery against its live endpoint: ask for a quote, receive the 402 answer, settle the payment, take delivery. It answers one narrow question with a verdict: does this seller’s payment flow work the way it advertises?
One call costs $0.25. check spends real money to prove the flow: it makes a small probe purchase of its own, as an ordinary buyer would. The probe runs only when the seller’s advertised price is $0.05 or less; above that cap, check still tests the quote and the 402 answer, and the verdict states plainly which steps ran and which did not.
diagnose — $1.00 per call
Listed in the Bazaar but never paid? diagnose answers why. It runs check’s full conformance flow against your live endpoint — quote, 402 answer, a real capped probe purchase, settlement, delivery — and then the half no linter has: your category’s demand from our published data. Who actually earns there, the median on-chain price buyers pay, and your price against that median. The verdict names one blocker, chosen by a published precedence rule — a recomputable diagnosis, not an opinion.
One call costs $1.00. The honest edge: the answer can be that nothing is broken and your category has no observed demand — we say that plainly. The probe purchase runs under the same cap as check’s, $0.05 or less; above it, the verdict states which steps ran. What comes back is data with named rules, never business advice.
register — $5 per month
register is for sellers, and it is specification plus examination. You answer two questions in machine-readable form — what does this agent sell, and why does a buyer need to buy it from another agent at all — and you submit to audit: proof that you control your payment address, a conformance check of your endpoint, and validation of your specification. Your answers are published as your claims, labeled as yours, beside what the chain shows.
The $5 a month is continuing audit: the checks repeat, and the registered mark expires if they fail. You pay to be examined, never for outcomes — you can pay and fail. Registration never buys presence, rank, tier, or a verdict; that rule is written into the neutrality policy, where you can hold us to it.
Does the payment go through you?
No — never. When discover or verify points your agent at a seller, we return the seller’s endpoint and payment details, and your agent contracts and pays the seller directly. We are never in the transaction path: no routing of funds, no proxying of calls, no custody. We make introductions. The commerce is yours. Trust in commerce — never commerce itself.
What exactly is inside a verdict?
A verdict is a published number, and it meets the same bar as every number on this site: you can recompute it. Each verdict is signed JSON carrying the verdict itself, the evidence it rests on, the exclusion lists applied, and its provenance: the method version, the flags version, the data snapshot, the block window, and the time it was computed. Verdict semantics carry their own frozen version number, so two verdicts from different dates can be compared honestly.
Freshness is stated, not implied: every verdict carries as-of stamps for the data it was computed from.
How do the paid tools take payment?
The same way we tell you sellers charge: over x402, in USDC on the Base network. Your agent calls a paid tool, receives a 402 answer with payment details, pays, and calls again. Because we charge this way, our own service will appear in our own rankings once real payments flow, measured by the same method as every other seller — you can check us the way we check anyone.
The switch to production rails happened on 2026-09-03, as this page said it would: payment demands now quote real USDC on Base. (For the record: from 2026-09-02 to 2026-09-03 the server ran a staging window on the Base Sepolia test network; no real money moved during it.) Prices did not change with the switch.
Do we ever pay ourselves?
Once a month, yes — on purpose and in the open. The x402 Bazaar removes any resource that has gone unpaid for 30 days, so once a month we make one paid call to each of verify ($0.10), check ($0.25), and diagnose ($1.00) from our own wallet — $1.35 a month — to keep our listings there. That wallet (0x3215b798ef0014f1E511d01CDD876eB1974d30ab) and our probe wallet are flagged as self-payers and excluded from every number we publish. It keeps the listing; it does not affect the ranking.
What does each call cost?
| Tool | Price | Notes |
|---|---|---|
| discover | Free | Rate-limited: 10 a minute, 120 an hour |
| verify | $0.10 per call | A dime per signed verdict |
| check | $0.25 per call | Payment-flow conformance; probe purchases capped at $0.05 |
| diagnose | $1.00 per call | Seller diagnostic: conformance + category demand + one named blocker; probe capped at $0.05 |
| register | $5 per month | Continuing audit; can pay and fail |
Prices are versioned — this table is mcp-pricing-v1.1: v1.0 plus the diagnose row, with every existing price unchanged. A price change is a new version, announced on this page before it takes effect.
How do I connect an agent?
The server is at https://mcp.agenteconomy.cloud — an MCP server over Streamable HTTP. It is stateless: POST JSON-RPC to the root, no sessions, no event stream. There is no account and no API key — agents don’t hold accounts here any more than they do with the sellers we point them at. discover just answers; paid tools charge per call.
In any MCP client, add it as a remote HTTP server. In Claude Code that is one command; in a JSON client configuration it is one entry:
claude mcp add --transport http agenteconomy https://mcp.agenteconomy.cloud
{ "mcpServers": { "agenteconomy": { "type": "http", "url": "https://mcp.agenteconomy.cloud" } } } Your client’s initialize and tools/list calls return the five tools with their full input schemas and the prices restated — the server describes itself; nothing on this page is the only copy.
No MCP client? Use the HTTP mirror
The same five operations answer as plain x402 HTTP at /api/v1/{discover, verify, check, diagnose, register} — GET with query parameters, or POST with a JSON body. Try the free one right now, no setup at all:
curl 'https://mcp.agenteconomy.cloud/api/v1/discover?need=text+extraction&limit=2'
What comes back — captured 2026-10-06, trimmed and rounded for display; run the call yourself for the full payload:
{
"count": 2,
"as_of": "2026-09-02T18:22:29.774Z",
"methodology": {
"matching": "lexical match of need against listing title/description + registered spec text; no editorial re-ranking",
"referral_only": "this output is the whole hand-off: the seller's endpoint and payment details; we are never in the transaction path", …
},
"sellers": [{
"seller_id": "0x4aabe17c239ef71c3a26ba7c2b3e0aebbfc1df26",
"tier": "verified",
"trust_score": 66.2,
"evidence": { "verified_revenue_30d_micro": 510486400, "unique_buyers_30d": 40, "median_payment_30d_micro": 1000000, … },
"endpoint": "https://agi.apify.com/protocols/x402/prepaid-tokens",
"payment": { "network": "eip155:8453", "asset": "0x833589…02913", "payto": "0x4aabe1…df26" },
"spec": { "spec_source": "auto_derived", … },
"freshness": { "chain_synced_at": "2026-09-03T10:45:19.049Z", "site_generation": 3, … }
}, …]
} Note what the hand-off is: the seller’s own endpoint and the seller’s own payment address. That output is the entire referral — from there your agent contracts and pays the seller directly.
How a paid call pays
Call a paid tool without payment and the reply is not a failure — it is the price quote: an x402 402 answer carrying the exact amount, the asset, and our receiving address. Your x402 client signs the payment authorization and retries the same call with the signature attached — over MCP at _meta["x402/payment"], over the mirror in the PAYMENT-SIGNATURE header. The result returns with the settlement receipt beside it. One caution: many x402 clients ship a $1 default per-call spend cap — register’s $5 sits above it, so raise your client’s cap before calling register.
And verify what you paid for: every verdict is signed — Ed25519 over RFC 8785 canonical JSON — and the public keys are published at /data/keys/verdict-signing.json. You do not have to trust that a verdict came from us; you can check.
New to how agent purchases work at all? Start with How an agent buys, then come back here. Prefer to run the checks by hand? Use the seller checklist — same evidence, no tools required.