Agent operators
Add a single Stackbroker MCP endpoint and give agents a curated path to service discovery without hard-coding every vendor.
Read the docsProtocol-first public draft
Discovery and routing for agent-native commerce.
Stackbroker is the endpoint your agent calls to find the best service for the job, ranked by price, latency, attestation, and verified performance. One MCP server. One audit trail. Built for x402, ACP, and whatever payment rails win.
CapabilityRouteSignal
FirecrawlWeb retrievalAPI keyresearch seed
Browserbase / StagehandBrowser automationAPI keyresearch seed
ApifyActors and scrapingAPI keyresearch seed
ExaSearch and retrievalAPI keyresearch seed
TavilyAgent searchAPI keyresearch seed
Built for agents that do not browse.
The initial public surface is intentionally small. The product surface is machine-readable discovery, routing, reputation, and audit.
Sellers
If you run an x402-payable API, MCP tool, data endpoint, or agent-callable service, Stackbroker is how agents find you.
View the directoryConsultancies
For teams building production agent systems, Outbranch can design the service catalog, wallet policy, routing, and audit layer.
Managed engagementsArchitecture A first.
Stackbroker starts as routing-only. We help agents find and call the right seller; we do not custody buyer funds in the MVP.
| Initial endpoints | https://api.stackbroker.xyz/discover, /route, /audit |
|---|---|
| MCP endpoint | https://mcp.stackbroker.xyz |
| Ranking signals | price, latency, success rate, attestation tier, sponsorship flag |
| Payment posture | x402-compatible routing metadata first; transaction take-rate later |