Security · transport · privacy

What you create
stays yours.

Your code, your prompts and your ideas pass through the gateway without ever stopping there. Nothing is kept, nothing trains a model, nothing is resold.
Request pathEU-FRA / TLS 1.3
01Client02API-AI03Model API
01
Hosted in Europe
02
TLS 1.3 · HSTS
03
Prompts never logged
04
No training on your data
05
No password to leak
91
Tokens / day
Aggregated across all keys
2
API formats
Anthropic and OpenAI
0
Prompt log bytes
Never written to disk
0
Streaming buffer
Every token relayed on the fly

Infrastructure

Where it all happens

A short, European, deliberately simple chain: fewer links, fewer risks.

01

Hosted in Europe

The gateway runs on a server in Europe. Few network hops, low and steady latency from France and the rest of Europe.

02

Always-encrypted transport

HTTPS required, TLS 1.2 and 1.3, HTTP/2 and HSTS: no request travels in the clear. Certificates renewed automatically.

03

One key, one scope

Your key only opens your balance. No shared credentials, no way to cross from one customer to another.

Data handling

Three commitments, no fine print.

Written simply. Applied strictly.

04

Your prompts are never stored

Every request streams through the gateway, then disappears. Never written to disk, never copied to a log, never replayed.

05

No model learns from you

API-AI doesn't run any model and doesn't train any: we're a thin routing and billing layer, nothing more.

06

Nothing is resold, nothing is tracked

No trackers, no analytics SDKs, no ad networks on the API. Your traffic is nobody else's business.

What we DO log

The bare minimum to run the service

Logged
  • Request timestamp, path, status code, duration
  • Model name + token counts (billing)
  • Source IP — kept for 14 days
  • Aggregate availability and error metrics
  • Purchase email address (sending the key, billing, support)
Never logged
  • Prompt content (system + user messages, system instructions)
  • Model responses or completions
  • Tool-call arguments or results
  • Request or response bodies
  • Card data — handled by our payment provider, never stored by us
REQUEST INSPECTOR

Open the hood: here's what the gateway forwards

Interactive example: pick a model, type a key (nothing is sent) and see what the gateway keeps, rewrites or strips before forwarding your request to the model. Your key is replaced, never forwarded.
Interactive exampleRuns locally · nothing is sent
clientyour machine
POST /v1/messages
Host: api-ai.app→ upstream provider
x-api-key: mdf-•••••3a7f
anthropic-version: 2023-06-01
User-Agent: anthropic-sdk-python/0.95.1→ api-ai-gw/1.0
X-Forwarded-For: 203.0.113.42
X-Request-Id: 01HV9X8K…
Content-Type: application/json
gatewayEU server · ~20 ms
  • kept
    x-api-key, anthropic-version, Content-Type
  • rewritten
    mdf- key → upstream key (never exposed) · Host → upstream · UA → api-ai-gw/1.0
  • stripped
    X-Forwarded-For, X-Request-Id, CF-Ray, client IP
  • tls
    1.2 / 1.3 · HSTS · ALPN h2
  • logged
    status, duration — never headers, never body
upstreammodel provider
HTTP/2 200
Server: upstreamremoved from the response
Via: 1.1 upstream-edgescrubbed on response
X-Request-Id: 01HV9X8K…scrubbed on response
Content-Type: application/json
anthropic-ratelimit-tokens-remaining: 493210
keptrewrittenremovedDetails on the Privacy and data page.

API-AI · API gateway

Your next idea is waiting for you.

The gateway is ready. Choose a balance and send your first request.

Explore docs