The trust & payments layer for the agent economy
Obolo is an MCP server gateway and marketplace. One endpoint, one API key per upstream API, and pay-per-tool-call from a prepaid balance — with hard spend caps and audit logs.
The problem
Thousands of MCP servers are published unverified. When an agent decides which tool to use and whom to pay, it has no reliable way to know who is behind a server, whether its schema changed without notice, or how much it will spend until it is already too late.
Obolo sits in the middle of that exchange. Instead of wiring your agent to dozens of endpoints with loose credentials and no limits, you connect it to Obolo: a single entry point with explicit trust and spend rules.
How it works
Obolo combines three pieces. A gateway that routes every tool call, enforces spend caps, and blocks dangerous destinations. A marketplace where servers are discovered and compared. And a merchant-of-record role: Obolo charges the buyer and settles with the publisher on an 80/20 revenue split.
Every server carries a verification tier — the trust signal an agent sees before it spends:
Indexed from a public directory. Metadata only: we know it exists and how it describes itself, but nobody has proven ownership.
The publisher proved ownership via DNS and registry, and the declared schema passed static analysis with a stable canonical hash. This is the line between "appears in a list" and "we verified who it is and what it exposes".
Who it is for
People building or running agents who need third-party tools without handing out credentials or risking runaway spend. One key, one cap, one log.
People who expose an API or MCP server and want to distribute it, charge for usage, and earn the verified badge. Obolo handles billing and settles 80% to you.
Payment rails
The prepaid balance can be topped up with Stripe, with prepaid USDC, or via x402. The agent spends against that balance; when it runs out or hits the cap, the gateway cuts off.
Early-stage note
Obolo is early-stage; this is a public draft (2026). The uptime, latency, and usage figures shown per server are illustrative placeholders and are labeled as such. What is real and verifiable is the ownership proof, the schema hash, and the spend accounting.
Contact
Obolo is run by the Obolo team. For questions, verification, or press, reach us at: hola@obolo.dev