# x402 & MCP Server Index (Tanod) > x402 endpoint and MCP server index: find paid APIs for agents, x402 checks and price benchmarks. A focused part of Tanod (https://tanod.dev/llms.txt covers every family), over HTTP and MCP. > > Pay per call in USDC on Base or Polygon or Solana or BNB Chain or Arbitrum with x402, or on Tempo with MPP; no account or API key. Free tier: a small daily per-IP > pool per family; over HTTP add the header `X-Tanod-Free: 1` to an unpaid call (without it every unpaid call gets the 402); over MCP > the free tier is automatic. > Every result is automated and heuristic, not an audit: findings can be false positives, and a clean result is not proof that code or a package is free of risk. > Tanod is operated by an autonomous AI agent on behalf of its owner. Scans run automatically; no person reviews individual results. ## API - [OpenAPI spec](https://agents.tanod.dev/openapi.json): machine-readable description of this family's 32 routes. - [x402 resources](https://agents.tanod.dev/.well-known/x402) - MCP: `https://tanod.dev/mcp/agents` (server `tanod-agents`); also at `https://agents.tanod.dev/mcp` on this host ## Routes - `GET https://agents.tanod.dev/v1/x402/pulse` (get_x402_bazaar_pulse_today_no_params): Use when an agent must decide what to list or price on x402: today's Bazaar listings, new sellers, payer gains and gaps. - `POST https://agents.tanod.dev/v1/x402/pulse` (get_x402_bazaar_pulse_new_listings_demand_gaps): Use when an agent must decide what to list or price on x402: today's Bazaar listings, new sellers, payer gains and gaps. - `POST https://agents.tanod.dev/v1/agents/uptime` (get_x402_mcp_endpoint_uptime): Use when an agent must know if an x402 endpoint or MCP server was up, with a valid 402, over the last 30 days. - `POST https://agents.tanod.dev/v1/agents/uptime/bulk` (get_x402_mcp_endpoint_uptime_bulk): Use when an agent must compare the 30-day uptime and valid-402 share of up to 25 x402 endpoints or MCP servers at once. - `POST https://agents.tanod.dev/v1/scan/package` (scan_mcp_server_agent_skill_package): Use when an agent is about to install an agent skill or MCP package and wants its code scanned first. - `POST https://agents.tanod.dev/v1/x402/payment-status` (get_x402_payment_authorization_status): Use when an agent must know if a signed x402 payment was used on-chain, can still settle or has expired, before paying again. - `POST https://agents.tanod.dev/v1/x402/receipt-check` (check_x402_payment_receipt): Use when an agent or seller must verify that a transaction hash paid a given token amount to a given address. - `POST https://agents.tanod.dev/v1/x402/well-known-file` (build_x402_well_known_file): Use when an x402 seller needs a /.well-known/x402 file for their domain, built from their own Bazaar listings. - `POST https://agents.tanod.dev/v1/x402/edge-check` (check_x402_edge): Use when an x402 seller behind a CDN or WAF must know if the 402 still reaches AI bots uncached and intact. - `POST https://agents.tanod.dev/v1/x402/price-benchmark` (x402_price_benchmark): Use when an agent must price an x402 endpoint against listed prices for similar ones: median, quartiles, closest listings. - `POST https://agents.tanod.dev/v1/x402/pay-test` (x402_ping): Use when an agent must test that its wallet and x402 client can pay, or health-ping on a schedule, with a signed receipt. - `POST https://agents.tanod.dev/v1/agents/preflight` (check_x402_endpoint_before_paying): Use when an agent must decide whether to pay an x402 endpoint: live 402, payTo change, price outlier, listing age. - `POST https://agents.tanod.dev/v1/x402/seller-report` (x402_seller_report): Use when an x402 seller wants one report on their endpoint: lint, price position, buyer preflight, Bazaar demand, fixes. - `POST https://agents.tanod.dev/v1/x402/listing-audit` (x402_listing_audit): Use when an x402 seller wants a full review of one listing: lint, 30-day demand, 10 nearest peers' prices, ranked fixes. - `POST https://agents.tanod.dev/v1/mcp/check` (check_mcp_server): Use when an agent must check that a remote MCP server is up, what it is and which tools it lists before connecting. - `POST https://agents.tanod.dev/v1/web/agent-readiness` (check_agent_readiness): Use when an agent must check whether a site is ready for AI agents: llms.txt, robots rules, sitemap, schema, OpenAPI, MCP. - `POST https://agents.tanod.dev/v1/x402/facilitators` (get_x402_facilitator_support_and_changes): Use when an agent must compare x402 facilitator schemes, networks, signers and fee changes since a date. - `POST https://agents.tanod.dev/v1/mcp/listing-audit` (audit_mcp_listings): Use when checking official MCP Registry/live drift. Endpoint host is sent to Smithery's public search. - `POST https://agents.tanod.dev/v1/mcp/list-preflight` (preflight_mcp_listing): Use when an agent must check an MCP server repo against a punkpeye awesome list's rules before opening a PR. - `POST https://agents.tanod.dev/v1/x402/repeat-demand` (get_x402_endpoints_with_repeat_paying_demand): Use when an agent must find x402 endpoints that buyers pay again and again, not one-off sweeps. - `POST https://agents.tanod.dev/v1/x402/clients` (identify_x402_client_by_user_agent): Use when an x402 seller must tell which User-Agent in its logs is a monitor, indexer, grader or HTTP library. - `POST https://agents.tanod.dev/v1/web/agent-traffic` (analyze_ai_agent_traffic_in_web_server_logs): Use when a site owner must see which AI crawlers, assistants, MCP clients and x402 buyers hit their server, from access logs. - `POST https://agents.tanod.dev/v1/web/log-audit` (audit_supplied_web_logs): Use when reviewing supplied web logs for referrer cohorts, self-referrals, asset links and bursts without fetching URLs. - `POST https://agents.tanod.dev/v1/apify/rules-check` (check_apify_store_rules_for_actors): Use when an Apify developer must check Actors for outside payment links, price claims and near-copies before Apify acts. - `POST https://agents.tanod.dev/v1/web/agent-readiness/fix` (generate_agent_ready_files_for_a_site): Use when a site failed an agent-readiness check and needs the files to publish. - `POST https://agents.tanod.dev/v1/watch/readback` (create_readback_watch): Use when an agent must keep checking that a live page or API answer still says what it shipped. - `POST https://agents.tanod.dev/v1/watch/readback/get` (get_readback_watch): Use when an agent needs the state and check history of a read-back watch it created. - `POST https://agents.tanod.dev/v1/x402/price-consistency` (x402_price_consistency): Use when a seller must find stale advertised prices that disagree with its unpaid 402 amounts. - `POST https://agents.tanod.dev/v1/agents/query` (search_x402_mcp_index): Use when an agent is looking for x402 endpoints or MCP servers by category, network, price or name. - `POST https://agents.tanod.dev/v1/agents/history` (get_x402_mcp_record_history): Use when an agent needs the price and availability history of one indexed x402 endpoint or MCP server. - `POST https://agents.tanod.dev/v1/agents/export` (export_x402_mcp_index): Use when an agent needs a filtered slice of the x402 and MCP index as JSON or CSV for its own analysis. - `POST https://agents.tanod.dev/v1/agents/delta` (agent_index_delta): Use when an agent already has an index copy and needs additions, removals and price changes since a snapshot or cursor. - `POST https://agents.tanod.dev/v1/agents/bulk` (download_x402_mcp_index_snapshot): Use when an agent needs the whole x402 and MCP index as one gzipped snapshot to load into its own store.