Developer kits · v1.0.3 · Oct 2026

Latitude 10 Agent Gateway

Every tool call your agents make goes through one door you control.

Three agents send tool calls through one gateway, which allows one, holds one for approval and denies one

What is the Latitude 10 Agent Gateway?

Put it between your agents and everything they call: MCP servers over HTTP or stdio, REST APIs and paid services. Each agent gets one MCP endpoint showing only the tools its policy allows, and every call is checked against that policy, held for a person’s approval when it should be, capped on what it may spend, and written to a tamper-evident audit log.

One YAML file for upstreams, agents and policies, reloaded live and testable in CI. Code you own: a TypeScript server that runs in Docker or on Fly.io, in front of the MCP clients you already use.

Want it installed for you? Ask for a fixed-price quote on the contact page.

You run this code and are responsible for it: review it, test it on staging, and check that it meets the laws, platform rules and security standards that apply to you before production. It is not legal, compliance or financial advice, and using it doesn’t make Latitude 10 your payment processor or service provider.

What do you get?

  • One MCP endpoint per agent over all your upstreams: MCP (HTTP or stdio) and REST APIs
  • Deny-by-default policies with argument rules, read-only rules and rate limits
  • Human approvals: an admin queue and Slack links, or the agent’s user in-band (MCP 2026-07-28)
  • Spend limits for paying agents: x402 and MPP price caps, daily and monthly budgets, a kill switch
  • Tool pinning: a changed tool description is held back until you review the diff
  • Upstream credentials stay in the gateway; a hash-chained audit log you can verify
  • Admin API and UI; Postgres or Supabase; deploys with Docker or Fly.io

Every kit includes

  • The full source code, yours to change
  • A setup wizard: node setup.mjs
  • A versioned release with a changelog
  • A download link that always serves the latest release

How do you set it up?

node setup.mjs

Writes your secrets and checks the policy file, then boots two demo upstreams behind the gateway (a stdio server it launches and an HTTP server with paid tools) with two agents, and proves it: filtered tools, an allowed call, a denial, a price cap, an approval that runs once, the HTTP proxy, and a verified audit chain.

You'll need: Node.js 22+. Optional: Docker or a Supabase project, a Slack incoming webhook, an OAuth provider.

Can an AI agent buy it?

An AI agent can buy this product for $79 on its own, paying in USDC over x402:

https://latitude10.tech/api/agent-products/agent-gateway

Or through our MCP server at https://latitude10.tech/mcp with buy_product. How agent payments work →

When an AI agent buys from Latitude 10, the person or company that runs the agent is the buyer and accepts the Terms of Service. Payments on a blockchain or over Lightning are final.

More developer kits

See all developer kits →
A Next.js frontend wired to a Rails API and a Postgres database, marked deploy-ready
Developer kits

Latitude 10 Starter Kit

A Rails API on Supabase Postgres and a Next.js frontend on Vercel, wired together and deploy-ready.

$19one-time
An AI agent gets HTTP 402 Payment Required, pays in USDC over x402 or over Lightning, and gets 200 OK
Developer kits

Latitude 10 Agent Payments Kit

Let AI agents pay for your API or MCP server with x402 and Lightning — as code you own.

$49one-time · launch price