Routing simulator
The routing simulator is an administrative diagnostic concept for asking: which Starfire route would this request be eligible to use, and why?
It is not intended to reveal proprietary routing algorithms. It explains effective eligibility and configured routing decisions at the product level.
A simulation can include concepts such as:
- plan
- organization context
- workload type
- requested model or routing mode
- required tools
- vision requirement
- context size
- structured-output requirement
- Research/FORGE eligibility
- provider health
Run a simulation
- Open the provider/routing administration surface.
- Open the routing simulator when available.
- Enter a representative request profile—not private user content.
- Choose the intended account/plan/organization conditions.
- Run the simulation.
- Review eligible routes, selected route, fallback, and exclusion reasons.
Useful exclusion reasons
A route can be excluded because:
- plan does not allow the model
- organization policy denies it
- required capability is missing
- context requirement exceeds configured limit
- provider/route is unhealthy
- feature rollout is disabled
- workload is not eligible for that model
Compare before and after configuration
Use simulation before publishing a routing change, then compare the expected decision after editing model availability, fallback, or policy.
Simulation is not execution
A route can be eligible in simulation and still fail during real provider execution because of a transient provider error, timeout, or rate limit.
Do not use routing simulation output to expose internal provider secrets, credentials, or proprietary scoring details to normal users.
