Calling Corti AI APIs from containers, serverless functions, or healthcare platforms? Your dynamic outbound IP changes on every deploy. Route speech-to-text, medical coding, and all Corti API calls through a dedicated static EU IP for HIPAA-compliant whitelisting.
import requests
# Route through static EU IP
# HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
proxies = {
"https": "https://user:pass@eu-01.outboundgateway.com:8443"
}
resp = requests.post(
"https://api.corti.ai/v1/transcribe",
headers={"Authorization": "Bearer YOUR_KEY"},
files={"audio": open("consultation.wav", "rb")},
proxies=proxies
)
Healthcare platforms and EHR systems require IP whitelisting for API access — but your infrastructure IPs keep changing
EHR systems, hospital networks, and healthcare platforms require IP whitelisting for API access. Patient data flows demand strict access controls.
Containers, serverless functions, and cloud deployments change IPs constantly. Your whitelisted IP becomes invalid on every deploy or scale event.
Compliance audits require stable, auditable outbound IPs for protected health information (PHI) flows. Unstable IPs trigger audit findings and access revocations.
Dev, staging, and production environments each need separate IP management. Different microservices call Corti from different IPs — unmanageable at scale.
"All API access must be restricted to approved IP addresses for HIPAA compliance."
You need one stable IP to give them — not an IP that changes with every deployment.
Your Healthcare App
HTTPS Proxy
(Static EU IP)
Corti AI API
Corti AI sees one fixed EU IP address — every API call from speech-to-text to medical coding to text generation.
HTTPS_PROXY as an environment variable — zero code changes required
Building healthcare applications with Corti APIs that need a stable outbound IP for HIPAA compliance and EHR integration
Running MedTech platforms with Corti-powered features that need IP-whitelisted API access for healthcare clients
Integrating Corti AI into hospital systems and EHR platforms with strict IP whitelisting and network security requirements
Ensuring HIPAA and GDPR compliance for healthcare AI integrations with auditable outbound IP trails
Set the proxy URL as an environment variable. All Corti AI API calls route through your static IP. No code changes needed.
Route Corti speech-to-text API calls through your static EU IP using the requests library.
# Set environment variable (recommended)
# export HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
import requests
import os
# Option 1: Uses HTTPS_PROXY env var automatically
resp = requests.post(
"https://api.corti.ai/v1/transcribe",
headers={"Authorization": f"Bearer {os.environ['CORTI_API_KEY']}"},
files={"audio": open("consultation.wav", "rb")}
)
# Option 2: Explicit proxy configuration
proxies = {
"https": "https://user:pass@eu-01.outboundgateway.com:8443"
}
resp = requests.post(
"https://api.corti.ai/v1/transcribe",
headers={"Authorization": f"Bearer {os.environ['CORTI_API_KEY']}"},
files={"audio": open("consultation.wav", "rb")},
proxies=proxies
)
Route Corti medical coding API calls through your static EU IP using fetch.
# Set in your environment or .env
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
// Use node-fetch or undici with proxy support
import { CortiClient } from '@corti/sdk';
// SDK auto-detects HTTPS_PROXY env var
const client = new CortiClient();
const result = await client.code({
transcript: "Patient presents with chest pain...",
codeSystem: "ICD-10"
});Works everywhere — Docker, Lambda, Kubernetes, CI/CD. Set it once, all Corti AI API calls use your static IP.
# Set in your environment, .env, or platform config
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
HTTP_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
# Most HTTP clients (requests, fetch, axios)
# automatically detect and use HTTPS_PROXY.
# No code changes needed.📖 Complete Documentation: For detailed examples, error handling, and advanced configurations, see our Python SSL Proxy Guide, Node.js Guide, and all other language guides.
EU-hosted infrastructure with GDPR and HIPAA-conscious data handling for your Corti AI healthcare integrations.
Corti is based in Denmark, and so is our proxy infrastructure. Your healthcare AI traffic stays entirely within the EU.
TLS passthrough means your patient data and API keys are never visible to the proxy layer. Meets both EU and US healthcare standards.
API traffic routes entirely within EU infrastructure. No detours through US servers that could complicate healthcare compliance.
One static IP provides a clear, auditable outbound identity for HIPAA security reviews and compliance audits.
One fixed IP for all Corti AI API calls. Whitelist it once in your healthcare platform settings. Works across all Corti APIs.
Set the HTTPS_PROXY env var. Your existing HTTP client automatically detects it. Your Corti integrations work as-is.
European data centers. GDPR-conscious setup. Perfect for healthcare businesses with EU compliance requirements.
Speech-to-text, medical coding, text generation, agentic framework — one static IP covers every Corti endpoint.
TLS passthrough means we can't see your traffic. Patient data, API keys, and medical transcripts stay private.
€29/month flat. No usage tiers, no per-request billing, no surprises. Cancel anytime.
Stop worrying about dynamic IPs blocking your Corti AI API access. Start using a dedicated, EU-based static IP for HIPAA-compliant healthcare integrations.
€29/month starter plan • 7-day refund policy • Direct founder support
We're happy to help you determine if OutboundGateway is the right fit for your Corti AI healthcare integrations.
Contact Our Founders →