Skip to main content
Routing with a general-purpose LLM usually means asking it to generate a destination name, then validating and parsing the text. With GLiDE, you define the allowed routes and receive one selected route plus a probability for every option. Use this pattern for support queues, agent tools, workflows, models, or any other pick-one routing decision. Add an other or human_review route when the listed destinations are not exhaustive.

Route a support ticket

choice is always one of your criteria keys. probabilities shows the complete distribution, while confidence is the margin between the two most likely routes. Tune the fallback threshold on representative traffic rather than treating 0.5 as universal.

What changes from an LLM router

  • The destination is constrained to keys you define; there is no generated text to parse.
  • You receive the full route distribution, not only a label.
  • You can send uncertain or out-of-scope cases to an explicit fallback.
  • You can ask several routing or scoring questions against the same state in one request.
See GLiDE Inference for authentication, limits, errors, and the complete response contract.