Compression control
Configuration recipes
Pick the workload that matches yours. Mintoken has four compression knobs and they don't all want to be on for every app — the recipe below shows which ones to flip and gives you a copy-paste snippet for creating the key.
01
Pick your workload
Closest match wins. You can fine-tune any toggle below afterwards.
Why this combination
Context compression cuts cache reads from repeated file reads in older turns. Lite intensity preserves code formatting and accuracy in responses.
02
Review or fine-tune
Live updating. Any change flips the recipe to Custom.
03
Copy-paste setup
Two snippets: create the key with these settings, then use the proxy.
Step 1 — Create the key with these settings
curl https://api.mintoken.dev/v1/auth/keys \
-H "Authorization: Bearer <SUPABASE_JWT>" \
-H "Content-Type: application/json" \
-d '{
"name": "production",
"intensity": "lite",
"smart_detect_enabled": false,
"auto_compress_input": false,
"context_compress": true,
"context_compress_level": "standard"
}'Step 2 — Use the proxy
curl https://api.mintoken.dev/v1/messages \
-H "Authorization: Bearer mt_live_..." \
-H "X-Provider-Key: sk-ant-..." \
-H "Content-Type: application/json" \
-d '{
"model": "claude-haiku-4-5",
"max_tokens": 512,
"messages": [
{"role": "user", "content": "Explain connection pooling."}
]
}'Or skip the cURL
Create the key from the dashboard with the same toggles — takes 30 seconds.