Orbis API Marketplace
Discover and call thousands of third-party APIs from your agent with marketplace browse, subscribe, and pay-per-call flows on Base USDC.
Overview
io.github.OrbisAPI/orbis-marketplace is a MCP server for the Build phase that browses 3,000+ APIs and calls them with x402 USDC pay-per-call on Base.
What is this MCP server?
- Marketplace positioning: 3,000+ APIs for autonomous agent use
- x402 USDC pay-per-call on Base blockchain
- Dual remotes: streamable-http and SSE endpoints on orbisapi.com
- Orbis API Marketplace title with site https://orbisapi.com/mcp
- Repository: OrbisAPI/orbis-sdk (marketplace v0.1.2)
- 3,000+ APIs stated in marketplace description
- Two remote endpoints: streamable-http and SSE
- Marketplace package version 0.1.2
What problem does it solve?
Indie builders waste days signing up for disparate APIs when the agent could discover and pay per call from one marketplace MCP.
Who is it for?
Agent builders who want a single MCP gateway to many paid APIs without individual vendor dashboards.
Skip if: Teams that need only one fixed REST integration with no micropayments or no Base/USDC wallet setup.
What do I get? / Deliverables
After you connect the Orbis remote MCP, your agent can search the marketplace, subscribe, and invoke APIs with USDC micropayments on Base.
- Agent-discoverable access to 3,000+ marketplace APIs
- Subscribe-and-call workflow without per-vendor MCP servers
- USDC metered API usage from a single MCP remote
Recommended MCP Servers
Journey fit
Composing external APIs into a product is core Build work; a marketplace MCP is where integrations get selected and invoked. Browse-subscribe-call is integration plumbing—wiring agent behavior to external services—not frontend polish or ship-time security review.
How it compares
Hosted API marketplace MCP with x402 billing, not a self-hosted OpenAPI code generator.
Common Questions / FAQ
Who is io.github.OrbisAPI/orbis-marketplace for?
Solo builders and agent authors who want autonomous browse-and-call access to thousands of APIs through Orbis with USDC pay-per-call.
When should I use io.github.OrbisAPI/orbis-marketplace?
Use it during Build when you are selecting and wiring third-party APIs into an agent or backend without building every SDK integration yourself.
How do I add io.github.OrbisAPI/orbis-marketplace to my agent?
Add remote MCP https://orbisapi.com/api/mcp (streamable-http) or https://orbisapi.com/api/mcp/sse (SSE) in your MCP client and fund x402 USDC on Base per Orbis docs.