429 failover
Route retryable provider failures through the router instead of teaching every agent app how to recover from exhausted provider keys.
Key balancing
Multiple API keys or authorized subscription paths can sit behind one provider profile with failover and load-balancing policy.
Modality safety
Image, audio, video, and document requests are constrained to capable models, and learned per-model modalities improve future routing.
Copyable 429 failover proof
# Sage Router 429 failover proof
# Goal: route through one OpenAI-compatible endpoint and let the router absorb retryable provider failures.
export OPENAI_BASE_URL=https://api.sagerouter.dev/v1
export OPENAI_API_KEY=sk_sage_your_key_here
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "sage-router/frontier",
"messages": [{"role": "user", "content": "Return one sentence about provider failover."}]
}'
# Inspect response headers for route/debug signals:
# X-Sage-Router-Provider
# X-Sage-Router-Model
# X-Sage-Router-Modalities
# Retry-After on hosted quota/rate-limit responses
# Public edge health:
# https://api.sagerouter.dev/edge/health
Copyable credential load balancing proof
# Provider credential pool shape
# Configure multiple authorized keys or subscription paths for the same provider.
providers:
openai:
loadBalance: round-robin
apiKeys:
- env: OPENAI_API_KEY_PRIMARY
- env: OPENAI_API_KEY_SECONDARY
ollama:
oauthPaths:
- ~/.ollama/primary
- ~/.ollama/backup
# Behavior:
# - pick a healthy credential according to policy
# - fail over on retryable 429/5xx responses
# - keep provider credentials on the trusted router host
# - expose one generated sk_sage key to apps and teammates
Copyable multimodal routing proof
# Multimodal routing proof
# Image/audio/video/document input should not be sent to text-only models.
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "sage-router/frontier",
"messages": [{
"role": "user",
"content": [
{"type": "text", "text": "Describe the image safely."},
{"type": "image_url", "image_url": {"url": "https://example.com/image.png"}}
]
}]
}'
# Router invariant:
# - route image requests only to image-capable models
# - route audio/video/document inputs only to capable models
# - exclude text-only GLM-style routes unless that model is declared or learned capable
# - record X-Sage-Router-Modalities for the served request
Copyable Reddit proof reply
If you want a concrete Sage Router proof path before wiring it into an agent, I’d test three things: 1. 429/provider failure behavior through one OpenAI-compatible endpoint. 2. Multiple authorized provider keys or subscription paths behind one provider profile. 3. Multimodal routing constraints so image/audio/video/document input only reaches capable models. Proof kit: https://sagerouter.dev/reliability-proof?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch&utm_content=proof-reply Public edge health: https://api.sagerouter.dev/edge/health 60-second setup: https://sagerouter.dev/quickstart?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch&utm_content=proof-reply The boundary: Sage Router sells routing, generated keys, quotas, telemetry, and reliability. It does not grant unauthorized provider access or ask people to paste provider credentials into public threads.
Next step
Run the hosted quickstart, compare the model routing calculator, or create a Pro generated key.