antcrew-proxy
A lightweight reverse proxy that lets you use antcrew-platform without ever giving the platform your LLM API keys.
How it works:
antcrew-platform → antcrew-proxy (yours) → api.anthropic.com
↑ ↑ api.openai.com
sends UUID token holds your real api.groq.com
(never sees keys) provider keys …
The platform generates a UUID token and sends it on every LLM request — one token covers all providers. Your proxy validates the token, substitutes the real API key for the target provider, and forwards the request. The platform never touches your keys.
Provider routing by URL path:
| Path prefix | Upstream |
|---|---|
/anthropic/… |
https://api.anthropic.com |
/openai/… |
https://api.openai.com |
/groq/… |
https://api.groq.com/openai |
/gemini/… |
https://generativelanguage.googleapis.com/v1beta/openai |
/moonshot/… |
https://api.moonshot.cn/v1 |
/deepseek/… |
https://api.deepseek.com/v1 |
/mistral/… |
https://api.mistral.ai/v1 |
/xai/… |
https://api.x.ai/v1 |
/together/… |
https://api.together.xyz/v1 |
/fireworks/… |
https://api.fireworks.ai/inference/v1 |
/cerebras/… |
https://api.cerebras.ai/v1 |
/ollama/… |
http://localhost:11434 (keyless) |
/lmstudio/… |
http://localhost:1234/v1 (keyless) |
/vllm/… |
http://localhost:8000/v1 (keyless) |
Setup (5 steps)
Step 1 — Generate a token in the platform
Go to Settings → LLM Mode, select your workspace, and open the Proxy section.
Enter the public URL where you will host this proxy (e.g. https://proxy.yourcompany.com) and click Generar token.
Copy the token — it is only displayed once.
Step 2 — Run antcrew-proxy
With Docker (recommended):
docker run -d \
--name antcrew-proxy \
-p 8080:8080 \
-e PROXY_TOKEN=YOUR_UUID_TOKEN \
-e ANTHROPIC_API_KEY=sk-ant-YOUR_KEY \
-e OPENAI_API_KEY=sk-proj-YOUR_KEY \
ghcr.io/iagop03/antcrew-proxy:latest
Configure only the provider keys you actually use — others can be omitted.
With docker-compose — copy docker-compose.example.yml, fill in your values:
docker compose -f docker-compose.example.yml up -d
Without Docker:
pip install -r requirements.txt
PROXY_TOKEN=your-token \
ANTHROPIC_API_KEY=sk-ant-... \
uvicorn main:app --host 0.0.0.0 --port 8080
Step 3 — Verify the proxy is healthy
curl https://proxy.yourcompany.com/health
# → {"ok": true, "providers": ["anthropic", "openai"]}
The providers list shows which keys are configured and will accept requests.
Make sure port 8080 is reachable from the platform host. Run behind a TLS terminator (nginx, Caddy, Fly.io, Cloudflare Tunnel) in production — the platform will send LLM traffic over HTTPS.
Step 4 — Activate proxy mode in the platform
Back in Settings → LLM Mode, click Proxy ×0.7. The workspace switches to proxy mode immediately.
Step 5 — Run a pipeline
Trigger any run from the platform. LLM calls are routed through your proxy; your API keys never leave your network.
Environment variables
| Variable | Required | Description |
|---|---|---|
PROXY_TOKEN |
Yes | UUID token generated by the platform |
ANTHROPIC_API_KEY |
No | Anthropic key (sk-ant-…) |
OPENAI_API_KEY |
No | OpenAI key (sk-proj-…) |
GROQ_API_KEY |
No | Groq key (gsk_…) |
GEMINI_API_KEY |
No | Gemini key (AIza…) |
MOONSHOT_API_KEY |
No | Moonshot AI key (sk-…) |
DEEPSEEK_API_KEY |
No | DeepSeek key |
MISTRAL_API_KEY |
No | Mistral AI key |
XAI_API_KEY |
No | xAI Grok key |
TOGETHER_API_KEY |
No | Together AI key |
FIREWORKS_API_KEY |
No | Fireworks AI key |
CEREBRAS_API_KEY |
No | Cerebras key |
ANTHROPIC_BASE_URL |
No | Override Anthropic endpoint |
OPENAI_BASE_URL |
No | Override OpenAI endpoint (e.g. Azure OpenAI) |
GROQ_BASE_URL |
No | Override Groq endpoint |
GEMINI_BASE_URL |
No | Override Gemini endpoint |
MOONSHOT_BASE_URL |
No | Override Moonshot endpoint |
DEEPSEEK_BASE_URL |
No | Override DeepSeek endpoint |
OLLAMA_BASE_URL |
No | Ollama server URL (default: http://localhost:11434) |
LMSTUDIO_BASE_URL |
No | LM Studio URL (default: http://localhost:1234/v1) |
VLLM_BASE_URL |
No | vLLM URL (default: http://localhost:8000/v1) |
HOST |
No | Bind host (default: 0.0.0.0) |
PORT |
No | Bind port (default: 8080) |
At least one provider key must be set (or a keyless local provider reachable), or all requests will return 503.
Adding a provider later
Stop the container, add the new key, and restart — no token rotation needed:
docker stop antcrew-proxy
docker run -d --name antcrew-proxy -p 8080:8080 \
-e PROXY_TOKEN=SAME_TOKEN \
-e ANTHROPIC_API_KEY=sk-ant-... \
-e OPENAI_API_KEY=sk-proj-... \ # new
ghcr.io/iagop03/antcrew-proxy:latest
Rotating the token
If you suspect the token is compromised, go to Settings → LLM Mode → Proxy → Rotar token. The old token is invalidated immediately. Update PROXY_TOKEN on your proxy and restart:
docker stop antcrew-proxy && docker rm antcrew-proxy
docker run -d --name antcrew-proxy -p 8080:8080 \
-e PROXY_TOKEN=NEW_TOKEN \
-e ANTHROPIC_API_KEY=sk-ant-... \
ghcr.io/iagop03/antcrew-proxy:latest
Revoking proxy mode
Click Revocar in the platform settings. The workspace reverts to managed mode and the token is deleted server-side. You can then stop the proxy container.
Security
- Token is validated with
hmac.compare_digest(constant-time) on every request. - Your real API keys exist only in your container's environment; the platform stores only the encrypted UUID token.
- The proxy has no persistent state — it validates, rewrites the auth header, and forwards.
- Use HTTPS in production (TLS terminator in front of port 8080).
Building locally
git clone https://github.com/iagop03/antcrew-proxy.git
cd antcrew-proxy
pip install -r requirements.txt
PROXY_TOKEN=test-token ANTHROPIC_API_KEY=sk-ant-... uvicorn main:app --reload
# Or build the Docker image
docker build -t antcrew-proxy .
docker run -p 8080:8080 -e PROXY_TOKEN=... -e ANTHROPIC_API_KEY=... antcrew-proxy
Metadata
Release files for antcrew-proxy 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| antcrew_proxy-2.0.0.tar.gz | 19.5 kB | Without provenance | Details for antcrew_proxy-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antcrew_proxy-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for antcrew_proxy-2.0.0-py3-none-any.whl |
Total release size: 28.8 kB
Release files / antcrew_proxy-2.0.0.tar.gz
| Download URL | antcrew_proxy-2.0.0.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89619d517d8e9ccd871026df63dcae1c8686b511c9fb7d2532ba59beda04dab2
|
|
BLAKE2b-256 checksum How to use checksums |
ebe3c1342882776484d84eb98e9fae2e5fa0d57537de4046581449f12f8f6dbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / antcrew_proxy-2.0.0-py3-none-any.whl
| Download URL | antcrew_proxy-2.0.0-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34d81827b5e3050425892f65518ed4001fbe6760465dc56ad6faa3ca3b597deb
|
|
BLAKE2b-256 checksum How to use checksums |
eae113aa355e3d116bb6ace6e5ecee0c30250ae8cfe4a595ba7e17d0cbb443ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for antcrew-proxy 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.