Gatewards MCP server

Gatewards SDK

Your agents can't burn more than you let them.

Official SDKs for Gatewards — a pipeline gateway for multi-agent systems. Caps fleet spend, detects runaway loops, dedups duplicate API calls across agents — drop-in proxy, no decorator, no code change inside your agents. Optional on-chain settlement via the open x402 protocol when you need it.

Why

AI agents fail while continuing to work. A retry loop, a verification chain with no terminator, a tool call that never resolves — these don't crash. They silently compound. One widely-discussed 2025 incident saw four agents stuck in an infinite conversation for eleven days before anyone noticed the invoice.

Dashboards and alerts tell you after it happens. Gatewards stops it mid-chain.

• Drop-in proxy. Point your agent at the gateway URL with a bearer token. No decorator, no callback handler, no framework adapter. Works with any framework that makes HTTP calls.
• Fleet budget enforcement. Cap what an entire pipeline of agents can spend. Breach once — every agent in the pipeline pauses.
• Multi-agent dedup cache. Five agents in the same pipeline call the same upstream API. The first request hits upstream; the next four are served from cache. Dedup happens across the pipeline, not per-agent.
• Runaway loop detection. Two agents in an infinite back-and-forth get flagged before the bill compounds.
• Optional: x402 settlement. When you do want on-chain payment for paid APIs — USDC on Base, sub-cent fees, sub-2-second settlement — the SDK implements the open x402 protocol end-to-end.

See it

You set a daily cap on a fleet. The fleet starts working. The cap hits. The gateway atomically blocks the rest and lands a signed webhook at your URL — all in one continuous run.

Each of the three guards is shown in isolation below.

Fleet budget cap

10 agents fire concurrent calls against a fleet capped at $0.50/day. Each call costs $0.10. Total intent: $1.00 — twice the cap. The gateway lets through exactly $0.50 worth and blocks the rest, atomically:

$ npx tsx scripts/demo-budget-enforcement.ts

  Gatewards — Fleet Kill Switch Demo

  You set the cap. Your fleet tries to overrun it.
  Watch the gateway hold the line.

  Your cap:    $0.50/day
  Fleet size:  10 agents
  They want:   $1.00  (200% of your cap)

  Fleet fires 10 concurrent calls...

  Agent-001  $0.10  ✅ allowed   (your cap: $0.50, used: $0.10)
  Agent-002  $0.10  ✅ allowed   (your cap: $0.50, used: $0.20)
  Agent-003  $0.10  ✅ allowed   (your cap: $0.50, used: $0.30)
  Agent-004  $0.10  ✅ allowed   (your cap: $0.50, used: $0.40)
  Agent-005  $0.10  ✅ allowed   (your cap: $0.50, used: $0.50)
  Agent-006  $0.10  ❌ BLOCKED   (your cap hit — pipeline paused)
  Agent-007  $0.10  ❌ BLOCKED   (your cap hit — pipeline paused)
  Agent-008  $0.10  ❌ BLOCKED   (your cap hit — pipeline paused)
  Agent-009  $0.10  ❌ BLOCKED   (your cap hit — pipeline paused)
  Agent-010  $0.10  ❌ BLOCKED   (your cap hit — pipeline paused)

  Result
    allowed:     5/10 calls
    blocked:     5/10 calls
    you spent:   $0.50  (your cap was $0.50 — not a cent over)
    overage:     $0.00  ← would have been $0.50 without the gateway

  You set the cap. The gateway enforced it atomically,
  even

The script runs the production guard code against an in-memory store — zero network, zero on-chain, ~1 second on a laptop. Source lives in the gateway repo.

Multi-agent loop

Shortened. The full README is on GitHub.