Semantic & exact caching
Serve repeat requests from the edge with configurable TTLs and custom keys.
A hands-on command center for Cloudflare AI Gateway. Send real requests through your custom hostname—or explore every control in a zero-key simulation.
https://housedoor.buggy-refreeze.uk
Compose an OpenAI-compatible request, inspect the exact headers, and see the gateway response—including cache and trace metadata.
Tokens stay in this tab’s memory and are never saved. Use BYOK or Unified Billing to avoid entering a provider token.
Ready when you are.
Your request trace will appear here.Model routing lives at the gateway, not in application code. Segment users, split traffic, enforce budgets, and fall back when a provider fails.
The request lab exposes request-level controls. Gateway-level features below are configured in Cloudflare and then applied consistently across providers.
Serve repeat requests from the edge with configurable TTLs and custom keys.
Recover from rate limits and provider failures with controlled retry strategies.
Enforce dollar budgets by provider, model, user, team, or application.
Inspect prompts and responses for unsafe content and sensitive data.
Centralize encrypted provider keys and protect the gateway with authentication.
Select a cost-effective model for each request while maintaining response quality.
Use logs, analytics, cost attribution, user insights, classifications, custom metadata, and OpenTelemetry to understand every request.
Your custom gateway hostname is already wired into the request lab.
Open the console ↗