QuotaGuard gives your AI agents, coding assistants, and MCP clients two fixed outbound IPs, so enterprise firewalls and API key allowlists accept them on every request.
Agents run on serverless and shared cloud infrastructure, so their egress IP rotates. Providers route API traffic from large shared ranges you can't pin. Every allowlist that should protect the agent breaks.
Route the agent's traffic through QuotaGuard, register the two IPs once, and every downstream allowlist has one stable identity to trust.
You give the agent a single outbound IP that a firewall admin, an API key setting, or a partner's allowlist can trust. The reason you need one is that agent infrastructure was built to scale, not to hold a stable address.
The tools agents call increasingly gate access by source IP. Composio restricts API keys to allowlisted IPs, OpenRouter offers an account-level IP allowlist, and Datadog blocks non-allowlisted API and MCP traffic. A key alone is no longer enough.
An agent on Lambda, Cloud Run, or a container changes its outbound IP on every deploy and scale event. Hosted LLM providers route from large shared ranges. Neither gives you an address you can put on an allowlist and keep.
Security teams approving agent traffic to model providers and MCP endpoints want one egress path they can allow and audit. A rotating or shared source IP means opening the firewall wider than anyone is comfortable with.
QuotaGuard sits between your agent and everything it calls. The agent's traffic leaves through your two fixed IPs, so one identity covers the model provider, the tool APIs, and the internal services behind your firewall.
Set the QuotaGuard connection URL and point the agent's HTTP client at it as a proxy. The same setup works on Heroku, Render, Railway, Fly.io, AWS Lambda, Vercel, Netlify Functions, Kubernetes, and direct VPS.
Your subscription includes two static IPs behind a load balancer. Register both wherever the agent's destinations allowlist, and traffic routes through whichever responds, so a single-node issue never stalls the agent.
Because the agent's outbound traffic all leaves through one known path, you can allowlist and audit exactly where it connects. That pairs with DNS-filtered and firewall-restricted environments where unmonitored egress is not allowed.
The setup is the same everywhere: a fixed egress IP the destination can allowlist. The specifics differ per tool. Start with the guide for the destination your agent depends on.
Both let you restrict API access to specific IPs, so a leaked key is useless from anywhere else. See the Composio static IP guide and the OpenRouter static IP guide for the exact allowlist mechanics.
Datadog's org IP allowlist blocks its public API, the Datadog MCP Server, and AI agent clients, while leaving telemetry ingest exempt. The Datadog static IP guide covers what is enforced and what is not.
Enterprise teams route coding assistants and model API traffic through a fixed egress IP so security can allowlist Anthropic and OpenAI endpoints. The setup is the one in Section 2. Talk to QuotaGuard support for help scoping an agent fleet.
Common questions about AI agent static IPs and QuotaGuard.
Does my AI agent need a static IP?
It does the moment a destination gates access by IP, which is now common for API keys, model providers, and enterprise firewalls. If your agent calls a tool that allowlists IPs, or runs inside a network that only permits approved egress, a rotating cloud IP will get it blocked. If nothing your agent touches restricts by IP, you don't need one yet. Most production agents hit at least one destination that does.
How fast can I set this up?
About 2 minutes. Add one environment variable and point the agent's HTTP client at QuotaGuard as its proxy. Then register your two static IPs wherever the agent's destinations allowlist. There is no infrastructure to rebuild and no change to where the agent runs.
Which agents and tools does this cover?
Any agent or client that makes outbound HTTP requests you can proxy, including custom agents, coding assistants like Claude Code, and MCP clients. On the destination side it covers tool APIs like Composio and OpenRouter, observability like Datadog, and model providers like Anthropic and OpenAI. The fixed egress IP is the same regardless of which one you're satisfying.
Should I use QuotaGuard Static or Shield for my agent?
Static satisfies the IP allowlist for most agent traffic. Use Shield when the data your agent moves is regulated PII, or your architecture is under SOC 2, PCI-DSS, or HIPAA review, because Shield uses SSL passthrough and does not decrypt the payload in ordinary operation. Agents that pass customer records or payment data to a model or tool are the typical Shield case.
Does this work with MCP servers?
Yes. An MCP client that makes outbound calls can route them through QuotaGuard the same way any HTTP client does, so a remote MCP server or an MCP-gated API sees your fixed IP. Datadog, for example, blocks MCP connections that are not on its org allowlist, and a QuotaGuard IP on that list is what lets the connection through.
Can I get a dedicated IP for an agent fleet?
Yes. Dedicated IPs are included on QuotaGuard Enterprise plans, at $219/month for Static and $269/month for Shield on direct billing. A dedicated pair is appropriate when a fleet's egress must not share an origin with any other organization's traffic. Contact QuotaGuard support after signup with your username and preferred region.
What about traffic coming back to my agent, like tool callbacks?
Those flow inbound to your endpoint, the opposite direction from the agent's outbound calls, and your inbound endpoint is unrelated to your egress IP. Inbound callbacks just need a reachable URL. If you want a fixed inbound endpoint for a callback receiver, QuotaGuard Static includes inbound proxy capability on direct plans starting at $19/month.
For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.
Get the fixed identity and security your application needs today.