onchain_agent_find_x402_service

shallow

ai.satohub/onchain-agents · Verify this server

USE WHEN an agent needs a paid API or data service it can call and pay per request with x402, and wants the ones with evidence behind them first. Find a paid API/data service an agent can call and pay per request with x402: market data, onchain data, web data, search, inference, security checks, identity lookups, dev tools and more. Describe the need in plain words; optional category, chain and max_price_usd narrow it. RULE ENFORCED: results are ranked by what Sato Hub observed, never by what a seller says about itself and never by anything paid to us. Order: (1) x402-style payments to the payout address on Base in the last seven days from several outside payers, not machine noise (counted when the transaction carries a signed USDC authorization, EIP-3009, the settlement x402's exact scheme uses; some non-x402 gasless sends use it too); (2) the listed URL answered HTTP 402 with a payment payload when we asked; (3) everything else, unknown before no. All USDC received at a payout address is context only and never ranks. Ties go to the lower per-call price. Each hit carries both readings with their dates and method, and links to the one canonical page for its payout address. `unknown` means we hold no reading, never that the service failed. A price is what the seller registered, not a charge we observed; `price_usd` appears only where the asset is USDC on Base or Solana. A hit is a description of what was observed, not an endorsement, and nothing here pays for or calls a service. NO HIT IS INVENTED: when nothing matches, the answer says so and names how to broaden (fewer words, drop a filter, another category). Returns (json): { hits: [{ url, network, chain, description, category, price_usd, merchant: { slug, display_host, pay_to, answers_402, payments, claimed_at, is_ours }, sato_url }], matched, capped, match_mode, evidence_as_of, ranking, guidance, unavailable }. `merchant.payments` carries the x402-style reading (the x402_* fields, which rank) and, as context only, the all-USDC reading. `sato_url` is the canonical page for the payout address. Read-only. Example: { need: "token prices", chain: "Base", max_price_usd: 0.01 }

No longer in the registry. The MCP registry stopped listing this server as of 20 Oct 2026. This report card stays available because the measurement was real, but the tool is excluded from search, rankings, and Vouch’s corpus counts. A published behaviour score is never recomputed or removed — it reflects what was measured while the server was listed.

100.0/100

1 trials · measured 16 days ago

onchain_agent_find_x402_service scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against ai.satohub/onchain-agents, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-06100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: onchain_agent_find_x402_service
[![Vouch score](https://vouch.tools/api/tools/666589a2-ad7a-4d31-8948-8709862436a8/badge.svg)](https://vouch.tools/tools/666589a2-ad7a-4d31-8948-8709862436a8)
onchain_agent_find_x402_service — Vouch