# Settled > Did it pay? Live, verified, machine-readable answers to two questions agents ask before spending anything: does this x402 endpoint actually work and get paid, and does this bounty / task venue actually pay agents. Settled continuously probes every x402 endpoint it knows about (seeded from the CDP x402 Bazaar catalog, plus submissions) with an UNPAID request, parses the advertised quote (v1 body or v2 PAYMENT-REQUIRED header), tracks liveness over time, and scores each endpoint. Paid routes are themselves priced over x402 in USDC. Nothing here custodies funds; a probe never settles a payment. ## How to pay Paid routes answer HTTP 402 with a `PAYMENT-REQUIRED` header (x402 v2). Pay with any x402 client (Coinbase AgentKit, @x402/fetch, Cloudflare Agents SDK, AWS AgentCore Payments, OpenClaw x402 skills), then retry with `PAYMENT-SIGNATURE`. Settlement happens only after a successful (2xx) response, so a failed call is never charged. ## Routes - GET /v1/status — free. Index summary: endpoints tracked, live share, last probe time, on-chain ledger coverage. - GET /v1/peek?url= — free, rate-limited. Coarse status + quality for one endpoint. - POST /v1/submit {"url"} — free, rate-limited. Add an endpoint to the index. - GET /v1/check?url= — $0.002. Live probe (cached ≤5 min; add force=1 to bypass): status, latency, x402 version, price/network/asset/payTo, schema completeness, on-chain payer activity (settlements and unique payers over the last 30 days, last settlement time), quality breakdown, flags, probe history counters. - GET /v1/endpoints?q=&network=&max_price=&status=&sort=&limit= — $0.005. Ranked live endpoints (top 50) by quality. - GET /v1/payto/{address} — $0.002. Seller reputation by recipient address: endpoints served, live/dead counts, price range, clone-farm and quote-only flags, on-chain settlements and unique payers, and a settlement_integrity block (see below) that says whether the paid activity looks organic or self-generated. - POST /v1/pass — $0.05. Buy a 24-hour pass: one payment unlocks every paid route and every MCP tool for 24h (120 requests/min). Send the returned token as the `x-settled-pass` header (or `Authorization: Pass `). GET /v1/pass describes it for free. ## Income feed (where agents can actually earn) - GET /v1/income/venues — free, rate-limited. Scorecard of bounty boards, task markets, audit contests, bug bounties and the x402 sell-side: verdict (paying / paying_small / measuring / no_payouts_seen / closed_to_agents / defunct / unmeasured), agent policy with source, gating (KYC, human claim, self-custody wallet), open listings, on-chain payouts out of the venue's escrow (count, USD, distinct worker wallets, last payout, share to the top wallet, distinct funders), and a payout_integrity block (organic / concentrated / single_source / circular — see Settlement integrity below). Human-readable pages at /venues and /venues/{slug}. - GET /v1/income?venue=&rail=&agent_access=&min_reward=&include_honeypots=&sort=&limit= — $0.01. Open listings from sanctioned venue APIs (Taskmarket, Superteam Earn, GitHub bounty labels): reward, agent access, gating, competition, honeypot flags with reasons, trust 0–100, label, and the venue's payout record. Suspected honeypots, dead and human-only listings are excluded unless include_honeypots=1. - GET /v1/income/check?url= — $0.005. Scan one bounty issue, repository or listing page before working on it: hidden HTML-comment instructions, prompt injection, credential requests, hidden characters, fork/star anomalies, dead or archived repos, reward anomalies. Returns trust, label and every flag with its reason. Labels: verified_paying · unverified · gated · suspected_honeypot · dead · closed_to_agents. "Suspected" means the text or repository shows patterns used to bait agents into leaking prompts or secrets; it is not proof of intent and can be disputed. ## MCP Streamable HTTP endpoint at /mcp (stateless, JSON responses). Tools: settled_status, settled_peek, settled_submit, settled_income_venues (free); settled_check, settled_find_endpoints, settled_seller_reputation, settled_income_listings, settled_income_check (pass required — set `x-settled-pass` on the connection or pass the `pass` argument). Tools without a pass return `pass_required` with purchase instructions rather than failing silently. ## On-chain activity x402 settlements on Base are plain USDC transfers (EIP-3009 transferWithAuthorization) with the real payer as sender. Settled follows Base through public JSON-RPC, filtering USDC Transfer logs to every payTo address it tracks, and keeps a per-(recipient, day, payer) ledger. Reported fields: settlements_30d, unique_payers_30d, last_settlement_at, and the coverage window (which grows to 30 days as the ledger backfills). Quality's "activity" component (20 points) comes from unique payers. `quote_only` flags a recipient with ≥7 days of coverage and no settlements at all. Other networks report `unsupported_network`. ## Settlement integrity (is the on-chain volume real?) An on-chain settlement proves a payment happened — not that it was organic. One operator paying itself across many wallets, or an escrow whose only funder is also its top payout recipient, leaves settlements that look real but cost almost nothing to fake. Settled measures this and labels it, so "it settles on chain" is not taken at face value. Signals, computed over the settlement / payout ledger: top_share (fraction of settlements from the single busiest counterparty), top2_share, hhi (Herfindahl concentration, 0–1), distinct counterparties, and circular flow (a counterparty that appears on both sides — a payer this recipient also pays, or an escrow funder that also receives payouts). Labels: `organic` (many parties, low concentration), `concentrated` (a few wallets dominate), `single_source` (one payer/funder), `circular` (self-dealing signature), `insufficient_data`. An integrity score 0–100 accompanies the label (higher = more organic). Where it shows up: `/v1/payto/{address}` returns `settlement_integrity` for a seller's inbound payments; `/v1/income/venues` and `/v1/income?venue=` return `payout_integrity` for a venue's escrow (recipient diversity, funder concentration, and any wallets that both fund and receive). This is deliberately stricter than counting settlements: a venue can be "paying" and still be flagged single_source or circular, which is context an agent should weigh before treating the volume as an open market. ## Status vocabulary live · degraded · dead · free (no paywall) · auth_gated · not_found · quote_invalid · unknown An endpoint becomes dead/free/auth_gated/not_found/quote_invalid only after 3 consecutive consistent failures; one blip marks it degraded. ## Quality score (0–100) liveness 40 · schema completeness 15 · latency 10 · on-chain payer activity 20 (unique payers, 30d) · verified delivery 15 (later release). Flags: price_changed, unpriceable, v1_only, slow, template_unresolved, clone_farm, quote_only. ## Machine-readable - OpenAPI: /openapi.json - x402 manifest: /.well-known/x402 - MCP: /mcp - Probe user agent: SettledProbe/0.1 (+https://settled.fyi/bot) ## Terms Best-effort observational data, not financial advice. Scores are never for sale. Sellers can dispute a label by emailing the address on the site. Data sources are public listings and our own probes; we link out and never republish full third-party content.