About nthbouncer

What we build

nthbouncer sits in front of an origin that cannot take unlimited concurrent traffic. You point a pool at an HTTPS API or a PostgreSQL database. Callers use a pool URL and a pool key. The control plane stores configuration and billing. The edge data plane admits traffic against your concurrency limit.

AI assistants connect through our MCP server at nthbouncer.com/mcp. They list pools, mint short-lived session keys, and call your origin without ever seeing the upstream credential. Scripts and CI use the Control API or the npm CLI.

Who it is for

Teams that share one vendor API account, one NetSuite concurrency cap, or one internal service with many concurrent callers. If every agent, job, and dashboard hammers the same origin, a pool gives them lanes instead of a race to 429.

Early access is open. New organizations receive 250k free requests to exercise real pools before choosing a paid plan. No credit card required.

Company

nthbouncer is built by a small team focused on agent-ready infrastructure. We publish docs, an OpenAPI spec, and MCP resources so automated clients can discover how to connect without a sales call.

Questions: [email protected]. Product and agent setup docs live at nthbouncer.com/docs.

Get started

Create an account, read the agents guide, or browse the llms.txt index for machine-readable links.