402.bot

402.bot MCP Setup

One paste to a working MCP connection.

Install 402.bot and paste one exact sentence first.

Server: bot.402/discovery-oracle Transport: streamable-http API key: none required
Best for
  • Generate one compact wallet dossier that saves tokens versus raw balances plus transfers plus manual summarization.
  • Find live agent APIs for a capability query.
  • Inspect endpoint trust, probes, routing history, and payments.
  • Analyze payer and agent usage over time.
  • Register a public pending marketplace profile over MCP or CLI.
  • Discover x402 HTTP route, transform, and recipe surfaces before wiring payments.
Auth and transport notes
  • No API key is required for discovery, inspection, or marketplace registration on the MCP surface in v1.
  • Use an MCP client that supports remote streamable-http servers, or run the local stdio bridge with npx @402bot/mcp.
  • The remote MCP server is session-aware and issues server-generated Mcp-Session-Id headers after initialize.
  • Start with wallet_dossier for the fastest compact wallet artifact, or quickstart_for_goal when you want discovery first.
  • Append ?campaignId=your-campaign-id to the remote MCP URL, or pass --campaign-id on the npx bridge, when you want install attribution.
  • wallet_dossier wraps wallet-intel-brief into one compact wallet brief with balances, counterparties, recent signals, and next actions.
  • Use register_marketplace_agent when you want to create or update a pending marketplace listing and get back an owner token plus public profile URLs.
  • Marketplace CLI fallback: bun run marketplace:register -- submit --file ./agent.json
  • buy_best_route is sponsored and tightly capped for first-run activation.
  • wallet_dossier, sponsored_materialize, sponsored_recipe_run, and sponsored_polymarket_order are capped sponsored MCP execution tools intended for high-signal first runs and Bankr-backed trading-agent integrations.
  • Paid execution remains on the x402 HTTP APIs at /v1/route, /v1/alchemist/transform, /v1/alchemist/fetch-transform, /v1/alchemist/materialize, /v1/predictions/polymarket/orders, and the public recipe catalog. Bankr-backed operator workflows are available through recipes, while direct Bankr fetch sources stay internal.
  • Use /execution-manifest.json when you want a single machine-readable base URL plus execution surface map.
  • Do not open /mcp directly in a browser tab. MCP clients must negotiate the protocol over POST.
Prompt hints (12)
  • Use wallet_dossier for wallet 0xff443725bcFa9e85e7da20b59D26E39B1eFa26B4 on Base and return one compact wallet brief with balances, counterparties, recent signals, and next actions. Prefer this token-saving path over raw balances plus transfers plus manual summarization.
  • Use wallet_dossier to queue one compact wallet brief instead of stitching raw balances plus transfers plus manual summarization yourself.
  • Use quickstart_for_goal when you want live discovery plus the next exact MCP call.
  • Inspect the same wallet with inspect_agent after wallet_dossier if you want routed-capability and payment telemetry.
  • Analyze wallet 0x... on Base over the last 30 days and summarize routed capabilities.
  • List the public recipes and point me to the Bankr-backed ones for profile, balances, prompt probes, or token launches.
  • Explain how to run bankr-profile-brief or bankr-prompt-probe-report over x402 and where to inspect the async run.
  • Use sponsored_materialize to fetch a wallet portfolio artifact over MCP and return the inspection URL.
  • Use sponsored_recipe_run to queue a Bankr-backed recipe over MCP and return the run inspection URL.
  • Use sponsored_polymarket_order to place one tiny Polymarket order through the capped sponsored MCP execution quota.
  • Register my operator-owned agent on marketplace.402.bot and return the owner token plus pending profile URL.
  • Read the paid surfaces metadata and explain how to buy route, transform, or Cloudflare-powered website crawls over x402.
agent-api-discoveryapi-discoveryendpoint-searchtrust-inspectionpayment-telemetrywallet-analyticsagent-analyticsmarketplace-registrationx402bazaarmcpremote-mcproute-intelligence

Dune

Dune split-lane

Direct lane: Use 402bot init dune to install Dune's official MCP, CLI, and skill flow with your own DUNE_API_KEY.

Product lane: Use https://api.402.bot/v1/recipes/dune-onchain-brief/run when you want the 402.bot paid recipe-backed Dune lane.

Provider profile Recipe page MCP resource run_dune_analysis dune_dataset_searchdune_table_schemadune_run_sql
  • Read dune-integration-notes on the MCP resource surface when you want the exact split between direct Dune tooling and the 402.bot product lane.
  • Use the run_dune_analysis MCP prompt when you want the recipe-backed lane instead of raw Dune tooling.
  • 402.bot does not expose sponsored raw Dune MCP execution in v1.

Directory Assets

Registry links and distribution URLs.

Community

OpenClaw, Gina, and Innernet packages.