Zero IP: A Static Proxy IP for Broker APIs

SEBI's retail algo trading framework changes how broker APIs are expected to work. API access should be authenticated, attributable to one user, auditable, and routed from a pre-approved static IP address.

That creates a practical problem for traders running bots from home internet, laptops, changing cloud machines, or any setup where the public IP can move. Your strategy can be correct. Your broker login can be correct. Broker API access still depends on the approved source IP.

Zero IP gives your bot one stable egress address for broker API traffic.

SEBI issued its circular on safer retail participation in algorithmic trading on 4 February 2025. The practical impact is simple for API users: open, unrestricted broker APIs are being replaced by controlled access with unique credentials, audit trails, and IP whitelisting.

For retail algo traders, this means API orders should come from a static IP that your broker can approve and trace. If your internet connection changes IP frequently, your automated orders can fail or fall outside the broker's allowed setup.

Manual trading through broker websites and mobile apps is largely unaffected. This requirement is aimed at API-based automated trading.

Zero IP gives your trading bot a dedicated IPv6 address. You whitelist that address with your broker once. After that, your broker API traffic exits through the same address every time.

Point any HTTPS-capable client at Zero IP, authenticate with your proxy key, and keep the same IPv6 egress for broker API whitelisting.

The proxy path is built in Rust because this layer should stay thin, predictable, and fast. It authenticates the proxy request, verifies the destination broker domain, selects your assigned IPv6 address, and moves packets with low overhead.

That matters for trading systems where routing should stay fast and predictable.

Your broker API session stays encrypted over HTTPS. Zero IP provides the fixed egress path and broker-domain allowlist checks.

For HTTPS broker APIs, the proxy establishes the tunnel and sees the destination hostname needed for allowlist checks. The broker request body and response body stay inside the encrypted session.

Zero IP is locked to approved broker API domains. Requests to supported broker hosts can pass through. Non-broker destinations are blocked at the proxy.

This keeps the product focused on one static route for trading APIs.

• Dedicated static IPv6 egress for broker API whitelisting
• Rust proxy path for high-throughput, low-overhead routing
• HTTPS CONNECT tunneling so broker API sessions remain encrypted
• Proxy API key authentication
• Header-based selection of your issued Zero IP address
• Broker-domain allowlisting for supported APIs
• Blocked egress to non-broker destinations
• No body logging for broker requests or responses
• A stable route that supports broker traceability under the SEBI framework

Zero IP handles the infrastructure part: keeping one stable IP between your bot and the broker API while you complete your broker's API onboarding, static IP registration, and algo compliance steps.