Freemodel Proxy — Reliable API Access

1. Quick Start: Direct Proxy

Using the freemodel proxy is straightforward. Grab your freemodel.dev API key from your account dashboard, set it as the Authorization header, and point your requests to our proxy endpoint instead of the upstream API.

Example request

curl https://fm.bluealitas.com/v1/messages \
  -H "Authorization: fe_oa_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "claude-haiku-4-5-20251001",
  "max_tokens": 128,
  "messages": [
    {"role": "user", "content": "Hello"}
  ]
}'

Claude Code multi-key

If you're using the proxy with Claude Code, you can pass multiple API keys in the FREEMODEL_API_KEYS environment variable as a comma-separated list. The system will automatically rotate through them for improved reliability.

FREEMODEL_API_KEYS="fe_oa_key1,fe_oa_key2,fe_oa_key3" \
  claude

2. Account & Multi-Key Setup

For the best reliability, create an account and consolidate your keys under one managed configuration.

How it works

1. Create an account on the Account page.
2. Add your freemodel.dev API keys, each with a tier and priority setting.
3. The system generates a single fmk_... internal API key for you.
4. Use the internal key for proxy authentication — the system auto-rotates through all your keys behind the scenes.

Example with an internal key

curl https://fm.bluealitas.com/v1/messages \
  -H "Authorization: fmk_YOUR_INTERNAL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "claude-haiku-4-5-20251001",
  "max_tokens": 128,
  "messages": [
    {"role": "user", "content": "Hello"}
  ]
}'

3. ⚠️ Critical Warning: Alt Detection

Please read this carefully. The upstream providers behind freemodel.dev employ anti-abuse and alt-detection systems. These systems are designed to detect multiple users routing traffic through the same server IP.

If multiple users all connect through the freemodel proxy without distributing their traffic across different IPs, the shared origin address can trigger these detection systems. The result is severe:

4. External Proxy Configuration

The solution is simple: each account can configure external HTTP/HTTPS/SOCKS5 proxies. The freemodel proxy rotates through your configured proxies on each request attempt, distributing traffic across different egress IPs.

This makes each request appear to originate from a different IP address, avoiding alt-detection triggers entirely.

How to set them up

1. Create an account on the Account page if you haven't already.
2. Navigate to the Proxies section of your account dashboard.
3. Add your proxies — you can use HTTP, HTTPS, or SOCKS5 protocols.

Where to find proxies

Public proxy lists are updated frequently. Services like proxifly and other proxy aggregators maintain lists that are refreshed hourly. Aim for at least 5–10 proxies from different IP ranges for effective distribution.

Example proxy URLs

http://user:pass@192.168.1.1:8080
socks5://192.168.1.1:1080
http://192.168.1.1:3128

Why this matters

Without external proxies, all your requests share the same egress IP managed by the freemodel proxy. This creates a fingerprint that upstream alt-detection systems can identify. Adding proxies distributes your traffic across many IPs, making it indistinguishable from natural, individual usage patterns.