← back to bouncer

Blog · September 2, 2026

Hello, agent!

Your AI is about to start calling real APIs. Today we're launching bouncer — the gateway that stands between your agent and the outside world, so every call is governed, logged, and (if you want) paid for.

Agents are getting tools. They browse, they query, they buy. But the moment you hand an agent a raw API key, you lose control: which tools can it call? How often? At what cost? bouncer answers all three.

What bouncer does

Point bouncer at any OpenAPI spec and it turns your API into an MCP endpoint — automatically, with a generated SKILL.md and a WebMCP snippet so agents can discover every tool. Then it puts a command center in front of it:

Governance

Allow/deny lists per tool, per-key rate limits, daily quotas and spend caps. Every decision logged.

OpenAPI → MCP

Import a spec, get a standards-compliant MCP server with tools/list and tools/call — no code changes upstream.

x402 payments

Charge per call in USDC via the x402 protocol. Agents pay with an X-PAYMENT header; you get a settled receipt in the log.

How it works

  1. Add an API — paste an upstream URL or import an OpenAPI spec.
  2. Get a proxied MCP endpoint (e.g. /api/public/gw/your-api) — clients never see your backend directly.
  3. Issue scoped API keys with rate limits, quotas and spend caps.
  4. Optionally flip on x402 and set a price per call.
  5. Watch every call land in the live log with its decision, latency and payment status.

That's it. Your API is now a governed, monetizable MCP endpoint — and your agents have a bouncer at the door.

Get started

Put a bouncer in front of your API.

Create a free account, import an OpenAPI spec, and get a governed MCP endpoint in a couple of minutes.

Sign up free Go to dashboard

No card required · sandbox payments included