Rank #7 of 7 in Model Gateways & Routers
Showcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Caching performance — stories about caching performance in this arenaCaching performanceevidence →
Stories about caching performance in this arena
Cost controls — stories about cost controls in this arenaCost controlsevidence →
Stories about cost controls in this arena
Key management — stories about key management in this arenaKey managementevidence →
Stories about key management in this arena
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservabilityevidence →
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Routing resilience — stories about routing resilience in this arenaRouting resilienceevidence →
Stories about routing resilience in this arena
Streaming tools — stories about streaming tools in this arenaStreaming toolsevidence →
Stories about streaming tools in this arena
Unified api — stories about unified api in this arenaUnified apievidence →
Stories about unified api in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Requesty stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · Official CLI · Full data export · Browse or query a catalog of available models with pricing and context-window metadata
Subscribe to events via webhooks
—–
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓7/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
n/an/a
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
n/an/a
Plug MCP servers into this product so it can use their tools
✓7/10
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
n/an/a
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Caching performance — stories about caching performance in this arenaCaching performance
Stories about caching performance in this arena
Cost controls — stories about cost controls in this arenaCost controls
Stories about cost controls in this arena
Key management — stories about key management in this arenaKey management
Stories about key management in this arena
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Routing resilience — stories about routing resilience in this arenaRouting resilience
Stories about routing resilience in this arena
Configure automatic fallback to another model or provider when one fails
✓8/10
Load-balance traffic across providers, deployments, or keys by weight, latency, or cost
~6/10
My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules
✓8/10
Smooth provider rate limits by spreading traffic across keys and queuing or throttling requests
~5/10
Set automatic retry policies for transient provider errors
~6/10
Streaming tools — stories about streaming tools in this arenaStreaming tools
Stories about streaming tools in this arena
Unified api — stories about unified api in this arenaUnified api
Stories about unified api in this arena
Sorted by importance (agentic first) (high → low) · 50/50 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Cclaimed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | n/a | untested | none yet | |
Call many model providers through one consistent API C One endpoint | developer | Unified api — stories about unified api in this arenaUnified api | 3 | full | 8/10 | Tprobed | |
Configure automatic fallback to another model or provider when one fails C Fallbacks | platform engineer | Routing resilience — stories about routing resilience in this arenaRouting resilience | 3 | full | 8/10 | Cclaimed | |
My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules C Policy routing | ai-native user | Routing resilience — stories about routing resilience in this arenaRouting resilience | 3 | full | 8/10 | Cclaimed | |
Point existing OpenAI-compatible code at the gateway by changing only the base URL and key C Compatibility | developer | Unified api — stories about unified api in this arenaUnified api | 3 | full | 8/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
Inspect logged requests and responses with latency, token counts, and cost attached C Logs | platform engineer | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 3 | partial | 6/10 | Cclaimed | |
Make tool and function calls across different providers with a consistent schema C Tool calling | developer | Streaming tools — stories about streaming tools in this arenaStreaming tools | 3 | partial | 6/10 | Cclaimed | |
Track spend per model, key, team, or user across all providers in one place C Spend tracking | platform engineer | Cost controls — stories about cost controls in this arenaCost controls | 3 | partial | 6/10 | Cclaimed | |
Stream token-by-token responses through the gateway from any provider C Streaming | developer | Streaming tools — stories about streaming tools in this arenaStreaming tools | 3 | partial | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Mint gateway-managed keys for teams and apps without exposing raw provider keys C Virtual keys | platform engineer | Key management — stories about key management in this arenaKey management | 3 | none | 0/10 | ||
Provision gateways, keys, and budgets programmatically through an admin API C Programmatic admin | ai-native user | Key management — stories about key management in this arenaKey management | 3 | none | 0/10 | ||
Set hard budgets and spend limits per key, team, or user C Budgets | platform engineer | Cost controls — stories about cost controls in this arenaCost controls | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Bring my own provider API keys and have the gateway use them for my traffic G Byok | developer | Key management — stories about key management in this arenaKey management | 2 | full | 8/10 | Cclaimed | |
Cache responses at the gateway to cut cost and latency on repeated requests C Caching | developer | Caching performance — stories about caching performance in this arenaCaching performance | 2 | full | 8/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
Load-balance traffic across providers, deployments, or keys by weight, latency, or cost C Load balancing | platform engineer | Routing resilience — stories about routing resilience in this arenaRouting resilience | 2 | partial | 6/10 | Cclaimed | |
Set automatic retry policies for transient provider errors C Retries | platform engineer | Routing resilience — stories about routing resilience in this arenaRouting resilience | 2 | partial | 6/10 | Cclaimed | |
Run traffic through gateway infrastructure that adds minimal latency overhead to provider calls C Latency | platform engineer | Caching performance — stories about caching performance in this arenaCaching performance | 2 | partial | 5/10 | Cclaimed | |
Smooth provider rate limits by spreading traffic across keys and queuing or throttling requests C Rate limits | platform engineer | Routing resilience — stories about routing resilience in this arenaRouting resilience | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Tprobed | |
Browse or query a catalog of available models with pricing and context-window metadata G Catalog | developer | Unified api — stories about unified api in this arenaUnified api | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Give an autonomous agent its own key with budget and rate guardrails so it cannot run away on spend C Agent guardrails | ai-native user | Cost controls — stories about cost controls in this arenaCost controls | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Request structured JSON-schema outputs across providers C Tool calling | developer | Streaming tools — stories about streaming tools in this arenaStreaming tools | 1 | full | 8/10 | Cclaimed | |
Export gateway logs and traces to my own observability stack G Integrations | developer | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 33 stories with headroom
What would move Requesty’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Cost controls — stories about cost controls in this arenaSet hard budgets and spend limits per key, team, or user
nonemoves PA Scoreimpact 30
The evidence pack shows analytics/usage tracking and BYOK/governance mentions, but no documentation of setting hard budgets or spend limits per API key, team, or user.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
The evidence pack covers routing, caching, guardrails, analytics dashboard, and pricing, but nothing describes exporting usage data, logs, or configuration in open formats or a data-portability/account-deletion path.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Requesty is presented as a hosted cloud gateway/router service (EU routing, hosted dashboard, per-usage pricing) with no evidence of a self-hosted deployment option, open-source repo, or on-prem package.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
The evidence pack covers routing, caching, guardrails, EU data residency, and BYOK, but contains no statement about a no-training policy or data opt-out for model training, so this claim is unevidenced.
Key management — stories about key management in this arenaProvision gateways, keys, and budgets programmatically through an admin API
nonemoves PA Scoreimpact 30
No evidence of an admin API for programmatically provisioning gateways, keys, or budgets; docs cover BYOK (manual key entry), analytics dashboard, and routing policies, but nothing about API-driven account/key/budget provisioning.
Key management — stories about key management in this arenaMint gateway-managed keys for teams and apps without exposing raw provider keys
nonemoves PA Scoreimpact 30
Missing: documentation of virtual/scoped key issuance, team/app-level key scoping, or key rotation/management APIs.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
Requesty's docs describe a real-time analytics dashboard for usage/cost/latency tracking, but nowhere is there evidence of AI-generated insights, recommendations, or suggestions derived from that data — the dashboard is purely observational reporting.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Requesty is presented as a unified LLM gateway/router with SDK compatibility and integrations (Claude Code, Cursor, etc.), but no evidence mentions an official Requesty CLI tool.
Showing the top 8 of 33 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 24 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Features docs20 stories
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Define rules that trigger actions automatically on events
- Cache responses at the gateway to cut cost and latency on repeated requests
- Run traffic through gateway infrastructure that adds minimal latency overhead to provider calls
- Track spend per model, key, team, or user across all providers in one place
- Bring my own provider API keys and have the gateway use them for my traffic
- Inspect logged requests and responses with latency, token counts, and cost attached
- Do everything through the API that I can do in the UI
- Choose where my data is stored (region/residency)
- Configure automatic fallback to another model or provider when one fails
- Load-balance traffic across providers, deployments, or keys by weight, latency, or cost
- My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules
- Smooth provider rate limits by spreading traffic across keys and queuing or throttling requests
- Set automatic retry policies for transient provider errors
- Request structured JSON-schema outputs across providers
- Make tool and function calls across different providers with a consistent schema
- Call many model providers through one consistent API
Quickstart docs10 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Bring my own provider API keys and have the gateway use them for my traffic
- Stream token-by-token responses through the gateway from any provider
- Request structured JSON-schema outputs across providers
- Make tool and function calls across different providers with a consistent schema
- Point existing OpenAI-compatible code at the gateway by changing only the base URL and key
- Call many model providers through one consistent API
requesty.ai7 stories
- Run traffic through gateway infrastructure that adds minimal latency overhead to provider calls
- Track spend per model, key, team, or user across all providers in one place
- My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules
- Stream token-by-token responses through the gateway from any provider
- Request structured JSON-schema outputs across providers
- Make tool and function calls across different providers with a consistent schema
- Call many model providers through one consistent API
llms.txt5 stories
OpenAPI spec2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
2 of 12 testable claims verified · 1 contradicted → integrity 0/100
14 distinct capability claims found in Requesty’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
2
Verified
9
Unverified
1
Contradicted
13
Undersold
Verified (2)
“Switch from OpenAI's API to Requesty by just changing the base URL — no SDK changes required”
Point existing OpenAI-compatible code at the gateway by changing only the base URL and keyfullproof ↗
“Single API gives access to 600+ models with intelligent routing, real-time analytics, and centralized governance”
Call many model providers through one consistent APIfullproof ↗
Unverified (9)
“Fallback policies automatically retry requests on a different model if one fails, keeping the app reliable”
Configure automatic fallback to another model or provider when one failsfullproof ↗
“On failure (timeout, rate limit, error), the router immediately retries the request against the next model in the chain”
Set automatic retry policies for transient provider errorspartialproof ↗
“Load balancing policies distribute requests across multiple models by user-defined weights”
Load-balance traffic across providers, deployments, or keys by weight, latency, or costpartialproof ↗
“Automatically caches long system prompts and repeated content to cut costs on providers that support prompt caching”
Cache responses at the gateway to cut cost and latency on repeated requestsfullproof ↗
“Supports bringing your own provider API keys (BYOK) for use through Requesty”
Bring my own provider API keys and have the gateway use them for my trafficfullproof ↗
“MCP Gateway lets AI coding assistants (Claude Code, Cursor, Roo Code) securely connect to MCP servers via Requesty's unified API”
Plug MCP servers into this product so it can use their toolsfullproof ↗
“Real-time analytics dashboard tracks costs, requests, tokens, cache savings, and latency across all models/providers”
Track spend per model, key, team, or user across all providers in one placepartialproof ↗
“Traffic can be routed through EU (Frankfurt) infrastructure so all processing/storage stays in the EU”
Choose where my data is stored (region/residency)partialproof ↗
“Every supported model can output structured JSON, from simple json_object mode to strict schema-enforced json_schema mode”
Request structured JSON-schema outputs across providersfullproof ↗
Contradicted (1)
“Provides access to 300+ models to choose the best one per coding task”
Browse or query a catalog of available models with pricing and context-window metadatanoneproof ↗
Undersold (13)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Run traffic through gateway infrastructure that adds minimal latency overhead to provider callspartialproof ↗
Inspect logged requests and responses with latency, token counts, and cost attachedpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
My agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rulesfullproof ↗
Smooth provider rate limits by spreading traffic across keys and queuing or throttling requestspartialproof ↗
Stream token-by-token responses through the gateway from any providerpartialproof ↗
Make tool and function calls across different providers with a consistent schemapartialproof ↗
Claims outside our story set (2)
Real capability claims found in Requesty’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Requests sharing the same trace_id or user_id are consistently routed to the same model”
source ↗“Guardrails scan AI request content for sensitive information before it reaches the model provider”
source ↗
Pricing signals
- 5%gateway feepay-as-you-goPay-as-you-go markup on model cost, no per-seat pricingsource ↗as of 2026-09-07
- 0%gateway feefree tierFree tier includes access to all free models, 200 requests/daysource ↗as of 2026-09-07
Extracted verbatim from the vendor’s own pricing page — hover a figure for the exact quote.
Business model
Free tier on free models (200 requests/day); pay-as-you-go routing adds a 5% markup on provider token prices with no per-seat fees; enterprise adds SSO, RBAC, and custom SLAs.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
