
SatGate – Economic Firewall for AI Agents
io.github.SatGate-io由 GitHub 账号 SatGate-io 发布v0.5.0更新于 Oct 24, 2026
Budget, payment and audit controls for AI agent API calls and MCP tool calls.
概览
SatGate 为 AI 智能体的 API 与 MCP 工具调用提供预算、支付策略和每次允许或拒绝的签名回执。
- 可以做什么
- SatGate 是部署在 API 和 MCP 工具前的网关。它计量智能体与 MCP 流量,在任务执行前执行所有者预算,并可对选定路由的外部智能体收费,每次允许或拒绝都会生成签名回执。它能解析 MCP JSON-RPC 工具调用,按工具归集成本,并支持可委派、可缩减预算的 macaroon 能力令牌。路由可采用 public、capability 或付费通道策略。
- 适用场景
- 当自主智能体调用付费 API 或 MCP 工具,且你需要硬性预算上限、按工具的成本归集或子智能体权限委派时适用。它适合希望在路由网关之外再加一层经济治理的团队。
- 运行要求
- 可使用托管的远程端点,或本地 npm 桥接包(stdio)。认证基于 OAuth;远程连接需要 SATGATE_URL 和 Authorization 请求头中的 bearer 令牌,本地桥接需要 SATGATE_TOKEN 环境变量。令牌在 SatGate Cloud 中签发。issue/pay/verify SDK 接口目前处于私有测试阶段。
安装
在 SourceWeft 中
- 打开 控制台中的 SatGate – Economic Firewall for AI Agents,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 SSE。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.SatGate-io%2Fsatgate/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"satgate-economic-firewall-for-ai-agents": {
"type": "sse",
"url": "https://satgate-mcp-saas.fly.dev/sse"
}
}
}README
SatGate
Observe, control and admit AI agent traffic
Every allow or deny comes with a signed receipt
[CI Status] [Go Report Card] [Go Reference] [License]
Why • Build • Features • Quick Start • Docs • Website • Blog
SatGate is a gateway in front of APIs and MCP tools. It meters agent and MCP traffic (Observe), enforces owner budgets before work runs (Control), and charges external agents on the routes you choose (Admit; the Charge policy in the dashboard). Every allow or deny comes with a signed receipt.
Try it as an agent. This hosted route returns HTTP 402 with a Lightning invoice and a macaroon. The price is 10 sats, and one payment buys access until the credential_expires_at time in that response, not just one request:
Agent instructions are in llms.txt.
Build Agents with SatGate
SatGate's developer primitive is three calls: issue(), pay(), and verify().
Install today:
The public packages install today; the issue/pay/verify API namespace is in private beta. Calls without private-beta access raise a structured error instead of returning fake receipts:
Runnable examples:
examples/python/issue_pay_verify.pyexamples/node/issue-pay-verify.mjs
Works with: MCP · OpenAI tools · Anthropic tools · LangChain · CrewAI · Raw HTTP
🎬 See SatGate in Action
☁️ Don't want to self-host? Try SatGate Cloud
Managed SaaS — zero setup, multi-tenant isolation, enterprise dashboard.
Free Observe tier. No credit card required.
The Problem
AI agents are making API calls autonomously. They spawn sub-agents, call MCP tools, and run overnight while you sleep.
Your existing stack answers: "Is this request authenticated?"
Nobody answers: "Should this agent have authority to spend, delegate, or invoke this paid resource?"
That's the gap. SatGate fills it.
What is SatGate?
SatGate is an Economic Firewall for AI agent requests. Drop it in front of your APIs and MCP tools to enforce scoped authority, budgets, paid-rail context, and Evidence Pack receipts before agents act.
Not another routing layer. Routing gateways (Bifrost, LiteLLM, Portkey) optimize which provider handles a call. SatGate governs whether the call should happen at all based on authority, policy, budget, and paid-rail context.
Use them together:
Features
- 🛡️ Capability Tokens (Macaroons) — Cryptographic credentials with built-in caveats, delegation, and next-request revocation. Not API keys — tokens that agents can safely sub-delegate.
- 🎯 MCP-Aware — Parses MCP JSON-RPC tool calls. Know that Agent X spent $47 on
search_databaseand $12 onsend_email— not just "1,000 requests." - 💰 Budget Enforcement — Hard stops per agent, team, or API. When the budget hits zero, requests are blocked. Not logged. Not alerted. Blocked.
- ⚡ Paid-Rail Governance — Govern paid API access across L402, x402, API-key billing, and enterprise ledgers without making any one rail the control plane.
- 🔒 Default-Deny — All routes require valid credentials unless explicitly public. Zero Trust by design.
- 🚀 <50ms Overhead — Lightweight Go proxy. Adds governance without adding latency.
- 📦 Self-Hosted — Your infrastructure, your rules. Single binary, Docker, or Kubernetes.
- 🔌 Drop-in — Works with any HTTP backend. REST, GraphQL, MCP servers. No code changes.
Quick Start
60-Second Demo
Try the three policies:
Public → Protected → Paid. Three policies, one gateway; paid rails are governed context, not the product boundary.
Hosted paid demo (Admit; Charge in the dashboard). No local Lightning node:
Unpaid calls return 402 with a Lightning invoice and a macaroon. The price is 10 sats, and one payment buys access until the credential_expires_at time in that response, not just one request. For Lightning, show the invoice to the owner, poll payment status, then retry. Poll rules are in llms.txt.
Other Install Methods
Configuration
Policy Types
How It's Different
Architecture
Key Concepts:
- Macaroons: Bearer tokens with embedded caveats (expiry, scope, budget, IP). Not API keys — they support delegation without server roundtrips.
- Delegation: Agent A gives Agent B a sub-token with reduced permissions and a $50 budget cap. B can't escalate.
- MCP Parsing: SatGate reads MCP JSON-RPC payloads to attribute costs to specific tool calls, not just HTTP endpoints.
- Paid-rail context: SatGate treats L402, x402, API-key billing, and enterprise ledgers as rails to govern around. Evidence Packs preserve which rail was involved without making the rail the product.
SDKs
MCP Proxy (NEW)
SatGate now includes a native MCP proxy that governs tool calls for any MCP-compatible agent:
- Budget enforcement: Hard 402 when agents exhaust their allocation
- Delegation: Parent agents mint sub-agent tokens with carved budgets
- Per-tool costs:
web_search: 5,dalle_generate: 50(wildcard patterns supported) - Two transports: stdio (local sidecar) or SSE/HTTP (remote multi-agent)
- Three auth modes: none, static token, macaroon (HMAC chain)
See pkg/mcpserver/README.md for full documentation.
Documentation
- Architecture Overview
- Quick Start Guide
- Configuration Reference
- Production Checklist
- Kubernetes Deployment
- LangChain Integration
- MCP Gateway Guide
☁️ SatGate Cloud & Enterprise
Self-hosting not your thing? SatGate Cloud is the fully managed version — same gateway, zero ops.
The open-source gateway handles protection, budgets, and paid-rail enforcement. SatGate Cloud adds the control plane:
- 📊 Observe — Real-time dashboards, usage attribution, cost center tagging
- 🎚️ Control — Budget and policy enforcement before agent requests execute
- 🤖 SatGate Mint — Zero-touch agent provisioning (K8s, AWS, OIDC)
- 🏢 Multi-tenant — Team isolation, RBAC, SSO/SCIM
- 📝 Audit — Tamper-evident logging, compliance exports
Start Free → (Observe is free, up to a fair-use cap)
Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
License
Apache License 2.0 — see LICENSE for details.
Links
- 🌐 satgate.io — Website
- 📝 Blog — Technical articles
- 🏢 Enterprise Governance — CISO/CFO/CTO use cases
- 💰 Pricing — Free Observe tier, Pro for enforcement
- 🔒 Security Model — Architecture & compliance
- 🧪 Sandbox — Try without signup
- 📊 ROI Calculator — Estimate savings
- ⚖️ Compare — SatGate vs Zuplo, Bifrost, cloud-native
- 📧 [email protected]
Built with ⚡ by SatGate — The Economic Firewall
来源:README.md,提交 9c94681
工具
0版本历史
1- v0.5.0最新Sep 29, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分