Discovery Oracle
Let your agent discover ranked live agent APIs, trust signals, payment telemetry, and x402 surfaces instead of guessing which endpoints exist.
Overview
bot.402/discovery-oracle is an MCP server for the Build phase that discovers live agent APIs, ranked endpoints, trust data, payment telemetry, and x402 surfaces.
What is this MCP server?
- Discovers live agent APIs with ranked endpoints and trust metadata
- Surfaces payment telemetry and x402-compatible API listings
- Remote MCP at https://api.402.bot/mcp (streamable-http)
- Beta server version 1.0.1-beta on MCP schema 2025-07-09
- Remote endpoint: https://api.402.bot/mcp (streamable-http)
- Published version 1.0.1-beta
- MCP server schema dated 2025-07-09
What problem does it solve?
Agent builders waste days hunting trustworthy, billable APIs because live endpoint lists and x402 readiness are fragmented and undocumented.
Who is it for?
Solo builders prototyping agent marketplaces, paid tool chains, or x402-aware workflows who need discoverability before writing glue code.
Skip if: Static CRUD apps with one known vendor API, teams that forbid beta discovery data in production routing, or non-agent traditional backends.
What do I get? / Deliverables
Your agent can query a centralized discovery oracle so integration plans start from ranked, telemetry-aware API candidates instead of blind web search.
- Shortlists of live agent APIs with ranking and trust context
- Visibility into x402 and payment-telemetry-ready surfaces
- Faster orchestration design before custom MCP wrappers
Recommended MCP Servers
Journey fit
Canonical shelf remains Build agent-tooling because most value lands when you implement agent routers; validate and operate are natural secondary touchpoints. Agent-tooling captures API discovery, x402 surfaces, and trust ranking as infrastructure for autonomous agents rather than a single REST wrapper.
How it compares
Agent API discovery MCP, not a single vendor integration skill or a generic OpenAPI generator.
Common Questions / FAQ
Who is bot.402/discovery-oracle for?
Indie agent developers and orchestrator builders who need ranked, trust-aware visibility into live APIs and x402 payment surfaces.
When should I use bot.402/discovery-oracle?
Use it during scoping and implementation when you are choosing which agent APIs to integrate, monetize, or fall back to—and when lists in docs are stale.
How do I add bot.402/discovery-oracle to my agent?
Add the remote MCP server https://api.402.bot/mcp (streamable-http) in your agent client’s MCP configuration; follow 402.bot docs if auth is required at runtime.