Agicap integrates with bank APIs and enterprise financial systems under maximum zero-trust. Route its outbound workers through two fixed EU IPs with one env var, so bank integrations clear security gates every time.
# Agicap integration worker env var
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
import requests
r = requests.get(
"https://bank-api.partner.eu/accounts",
headers={"Authorization": "Bearer .."}
)
Banking and enterprise financial systems enforce maximum zero-trust security. Dynamic cloud egress breaks the integrations Agicap depends on.
Banks and enterprise financial systems operate under zero-trust. They require every API caller to come from a known, allowlisted IP. When Agicap's cloud workers get a dynamic egress IP, bank integrations fail because the source is unrecognized.
Agicap connects to many banks and ERPs, each with its own firewall and IT approval process. Without a single fixed IP, every client onboarding becomes a multi-week security negotiation that restarts whenever the cloud IP rotates.
Agicap processes cash flow data for French and European enterprises. Those clients and their banks expect the integration traffic to stay within EU jurisdiction. Dynamic egress from US cloud regions raises compliance flags.
Agicap's integration workers run as managed processes in the cloud. They don't have access to VPC settings, Cloud NAT, or routing tables. The only lever available is what the worker code sees as environment variables.
"What IP will Agicap use to access our API? We need it allowlisted before we activate the integration."
You need one fixed EU address that never changes, so every bank can approve it once and move on.
Agicap worker
HTTPS Proxy
(Static EU IP)
Bank API
Every call Agicap's workers make to bank APIs or enterprise ledgers leaves from the same pair of EU addresses. Banks allowlist both once, and every future sync passes their security gates. Two IPs with automatic failover.
requests or fetch, setting HTTPS_PROXY is all it takes.Building and running the integration workers that sync cash flow data from bank APIs and enterprise financial systems.
Coordinating with client banks and ERP vendors to get Agicap allowlisted under their zero-trust security policies.
Client-side security who need to allowlist Agicap on their bank API firewalls and want a stable, predictable EU address.
Accountable for where financial data is accessed from, who want a documented EU egress rather than rotating cloud IPs.
Set HTTPS_PROXY in Agicap's integration worker runtime. Outbound calls to bank APIs then leave through your fixed EU IP.
If Agicap's worker code uses requests, setting HTTPS_PROXY is all you need.
# env var in Agicap worker runtime
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
BANK_API_TOKEN=your_bank_token
import os
import requests
# requests honours HTTPS_PROXY from the environment
r = requests.get(
"https://bank-api.partner.eu/accounts",
headers={"Authorization": f"Bearer {os.environ['BANK_API_TOKEN']}"},
)
print(r.status_code) # 200, from your fixed EU IPIn Node, pass the proxy explicitly with https-proxy-agent.
// env var set in the worker runtime
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
const { HttpsProxyAgent } = require('https-proxy-agent');
const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY);
// Every bank API call leaves through your fixed EU IP
const res = await fetch('https://bank-api.partner.eu/accounts', {
headers: { 'Authorization': 'Bearer ..' },
agent,
});Two IPs, one pair for all banks
Your account comes with two static IP addresses (for example 51.xx.xx.10 and 51.xx.xx.11). Every bank allowlists the same pair. If one proxy node is briefly unavailable, traffic shifts to the other automatically. No bank sees a disruption.
📖 Want the longer version? Worked examples, error handling, and other languages are in the Python SSL Proxy Guide, Node.js Guide, and the rest of the docs.
Agicap is French. The outbound path to bank APIs should stay in Europe.
The proxy runs in EU data centres, so Agicap's integration traffic to bank APIs leaves from European infrastructure, matching what EU financial compliance teams expect.
Because TLS passes straight through, the proxy never decodes financial data, auth tokens, or sync payloads. It forwards encrypted bytes; it doesn't read them.
Integration traffic doesn't bounce through US infrastructure on its way to a bank API, keeping the data path inside the EU.
When a bank's security team asks what IP to allowlist, the answer is two fixed EU addresses that never change. No rotating cloud pool, no refresh cycle.
Two addresses for every bank to allowlist, with automatic failover. Onboard once, never update.
Send the IP pair to a bank's security team once. They allowlist it and cash flow sync works from day one.
European data centres and a GDPR-conscious setup. Agicap is French, so your traffic stays in the EU.
Banks see a predictable, known source for every API call, which is exactly what zero-trust security requires.
TLS passthrough means the proxy can't read your traffic. Financial data and auth tokens stay private.
Starting from €19/month. Flexible plans for every scale. Cancel anytime.
Stop letting dynamic cloud egress break bank API integrations under zero-trust. Give every bank one stable pair of EU IPs to allowlist.
€19/month starter plan • 7-day refund policy • Direct founder support
Agicap runs its integration workers on cloud infrastructure, so the outbound IP depends on the cloud provider's dynamic pool. When those workers need to reach bank APIs that enforce zero-trust IP allowlisting, the dynamic IP gets blocked. OutboundGateway gives Agicap a fixed pair of EU IPs that banks can allowlist on their firewalls once, and every future sync passes.
You send the two fixed EU IP addresses to the bank's security team. They add both to their API firewall or zero-trust access rules. The pair never changes, so the allowlist entry is permanent. No refresh cycle, no re-approval.
Agicap processes cash flow data for French and European enterprises. Those clients and their banks expect the integration traffic to stay within EU jurisdiction. OutboundGateway routes through EU data centres owned by an EU company, so the full data path stays within EU jurisdiction and satisfies GDPR and financial compliance requirements.
Happy to talk through how a two-IP EU egress fits your Agicap integration pipeline, whether you're connecting to 5 banks or 50.
Contact Our Founders →