Give agents a pass, not the password.

Connect Claude, Cursor, GrokBot, or any MCP client to a data warehouse, vendor API, or your own apps. Let them swarm in lanes.

Start a pool

250k free requests to start. Early access. No credit card, no expiration.

Swap the origin for a pool URL.

curl
+ curl https://api.inventory.example.com/services/rest/record/v1/customer/42 \
+ -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9..." \
+ -H "Content-Type: application/json"

Callers carry a pool key. The vendor secret never reaches the client.

Don't hand it the credentials.

Callers authenticate with a pool key. They never receive the API secret or the database password.

Let it swarm in lanes.

The swarm gets through. They share the same N, so the origin never sees more than that at once.

Nothing to deploy.

No sidecar, no library. A pool is a hostname you point traffic at.

How a pool works

Grant access to HTTP and PostgreSQL with a hard concurrency limit.

Upstream credentials

The pool attaches the upstream credential. Callers authenticate with a pool key and never receive the API secret or the database password.

Hard concurrency limit

Set max concurrency once. Every caller draws from the same slots. Anything above N waits until a slot frees.

Adaptive limit

When you do not know N, adaptive mode reads upstream 429s and settles just below the limit it finds.

PostgreSQL

Front a database the same way. Callers send SQL over HTTP to the pool hostname. Queries compete for the same N, and they never receive the database credential.

Async admission

When waiting in queue would take too long, the pool accepts the work, returns 202, and posts a signed webhook when the origin responds.

Simple pricing

Monthly or yearly. Start with 250k free requests. No credit card.

Starter

One origin, first pools

$29/month
  • 8 pools · 10 concurrent
  • 500k requests / mo
  • *.nthpool.cloud · 0 custom domains
  • 1 origin per pool
  • then $1.00 per 100k requests

Team

Shared origin across apps

$79/month
  • 20 pools · 20 concurrent
  • 5M requests / mo
  • *.nthpool.cloud · 10 custom domains
  • Async admission + access gates
  • Origin capacity budgets
  • then $1.00 per 100k requests

Business

Org capacity + auto balance

$199/month
  • 40 pools · 50 concurrent
  • 20M requests / mo
  • *.nthpool.cloud · 50 custom domains
  • Everything in Team
  • Auto-balance capacity
  • then $0.80 per 100k requests

On every plan

  • Fixed + adaptive concurrency
  • HTTP or PostgreSQL backends
  • Bounded queue + wait budget
  • RPM limit
  • Retry on upstream 429
  • Response cache
  • Pool keys + inbound HMAC
  • Upstream credentials
  • Concurrency locks API
  • Metrics + email alerts
  • Access logs + tags
  • Spend caps + usage emails
  • Organizations + invites

Plan tiers set your pool and concurrency limits. Request overage applies after the monthly allowance.

Need more?

Higher concurrency, more pools, or longer log retention. We'll size a custom plan.

Questions

Can my AI assistant use a pool?

Yes. Add https://nthbouncer.com/mcp. No token to paste. Approve which pools. The assistant gets a short-lived key, default read-only, and never sees the origin credential. It shares the same N as every other caller.

Can it front a third-party API?

Yes. Point a pool at the provider's HTTPS API. The pool attaches the upstream credential. Callers carry a pool key, not the vendor secret.

Can it front my own API?

Yes. Point a pool at your HTTPS origin, then route each caller through the pool endpoint. Nothing changes but the hostname.

Can it front PostgreSQL?

Yes. Point a pool at your database. Callers send SQL over HTTP to the pool hostname. Every query competes for the same concurrency limit, and they never receive the database credential.

Do you store my upstream credentials?

The dashboard never keeps the secret, not even a hash. The edge encrypts it on save and decrypts it only inside an isolated sandbox to reach your origin. Callers never see it. Rotate it from Credentials and every attached pool updates.

How is this different from a rate limiter or an API gateway?

A pool is a concurrency governor. It counts requests in flight and holds the rest at the gate. A rate limiter counts requests per window. A gateway publishes and shapes APIs. Use a pool when the origin allows only N simultaneous calls.

Open the pool and let your agents swarm.

250k free requests to start. Early access. No credit card, no expiration.

Try for free