Skip to main content
The Playground lets you see how any prompt will be routed before it hits production. Use it to verify tier classification, check cost estimates, and debug unexpected routing decisions.

​
How to Test a Prompt

  1. Open Playground from the dashboard sidebar
  2. Type or paste your prompt into the input box
  3. Click Route or press Ctrl+Enter

​
Reading the Result

After routing, you see a result panel with:

​
Tier Badge

Shows which tier was assigned, for example STANDARD. Color-coded:

​
Selected Model

The model Routor would use for this request. Shown as provider/model-name, for example deepseek/deepseek-v4-pro or google/gemini-3.5-flash.

​
Confidence Score

How certain the classifier is about the tier assignment, from 0 to 1.

​
Cost Estimate

Shows the estimated cost for this request on the selected model vs what it would have cost on a baseline model like Claude Opus 4.8. Example:

​
Method

How the tier was determined.

​
Fallback Chain

The ordered list of models Routor would try if the primary fails:

​
Testing Against a Profile

To see how a prompt routes under a specific profile:
  1. Select the profile from the profile bar above the input box - it shows the profile’s name, tier constraint, and cost cap
  2. Type your prompt and click Route
The result reflects the profile’s tier floor, ceiling, and capability caps, plus a routing trace showing each step the decision went through and the savings vs. baseline. Playground test result under a profile - profile bar, routing decision, routing trace, and selected model with savings

​
Why a Decision Might Surprise You

If a prompt is routed to a higher tier than expected, these are the most common reasons:
  • Code keywords detected - even mentioning function names or syntax can bump the tier
  • Multi-step patterns - numbered lists or “first… then…” patterns score higher
  • Long context - a large system prompt or long conversation history pushes toward COMPLEX
Use the Debug Endpoint to see exactly which dimensions fired and what score they contributed. That tells you precisely why the tier landed where it did.

​
Example Prompts to Try

These cover the full tier range and help you understand how the classifier works: Run each one and compare the confidence scores to build intuition for how the classifier works.

​
What the Playground Does Not Do

  • It does not make a real API call to the model. It only runs the routing decision.
  • It does not charge credits for testing prompts.
  • It does not show the actual model response, only the routing decision.
To see a real response, use the actual API with your app or a tool like Postman.