Direct-connect vs. the Obolo gateway
An agent can connect to each MCP server directly, or route through the Obolo gateway. Both paths are valid; they have different trade-offs. Here’s the comparison, dimension by dimension.
| Dimension | Direct-connect | Obolo gateway |
|---|---|---|
| Trust / verification | You trust each server as you find it; no standardized ownership or schema signal. | Two tiers: “crawled” (indexed metadata) and “verified” (ownership via DNS + registry and a schema with a canonical hash). |
| Billing / payments | Each server charges its own way (or is free); you integrate and reconcile one by one. | Single merchant of record: pay per call from a prepaid balance, 80/20 split to the publisher. Stripe, prepaid USDC or x402. |
| Spend control | Caps are yours to build in the client, server by server. | Hard spend caps per key; when reached, the gateway returns a 429 and never overcharges. |
| SSRF / security | Your runtime opens outbound connections to every host; you absorb the SSRF and rebinding risk. | The gateway mediates the connection and applies its own egress posture; the agent talks to one trusted host. |
| Drift / rug-pull protection | If a tool’s schema or behavior changes, nothing catches it. | The verified schema has a stable canonical hash; if the real one deviates, it’s detected and payout is frozen. |
| Endpoints and keys | Many endpoints and many credentials, each with its own format and rotation. | One endpoint per API behind a single pattern; one `obl_…` key per API, with its own tool view and cap. |
| Merchant of record | None; each billing (and tax) relationship is between you and each publisher. | Obolo is the merchant of record: it handles billing, taxes (incl. Latin America) and settles publishers. |
The honest trade-off
Direct-connect has fewer layers: no intermediary in the data path and no gateway margin to pay. In exchange, trust, billing, caps and drift protection are on you. The gateway adds a network hop and a merchant-of-record model; in exchange, it centralizes verification, payments and spend control in one place. Choose based on how much of that you want to build and operate yourself. MCP gateway, security.
Frequently asked questions
An MCP gateway is an intermediary that sits between an agent (MCP client) and one or more MCP servers. It presents a single endpoint and one key per API, and along the way adds trust verification, per-call metering and billing, spend caps and audit logs. Obolo is such a gateway, plus a marketplace.
Neither exactly: it sits in the middle as a gateway/proxy. Toward your agent it behaves like an MCP server (it exposes tools over Streamable HTTP + JSON-RPC 2.0); toward the upstream server it acts as a client. That middle position is what lets it verify, meter and charge.
With a DNS-TXT challenge: the publisher adds a TXT record on their domain to prove control. Proven ownership is required to reach the verified tier and to settle payouts.
Stripe, prepaid USDC and x402. The buyer funds a prepaid balance and each call is deducted from it; the publisher gets paid its 80% via Stripe Connect or USDC.
Docs · Monetize an MCP server · Glosario · Publisher
Public draft, 2026. Per-server figures (uptime/latency/usage) are illustrative placeholders.