Decision gates Coming soon
Set fine-grained boundaries.
Add an optional gate in front of any model. You write the question a decision model answers. Each possible answer gets its own route, whether that is a different model or a dropped request. AllModels runs the decision and the inference in a single API call, so your application calls one gated model ID.
Your rules, one model ID
Build hybrid models from any decision.
Abliterated models will answer almost any prompt, so the controls belong in your routing rather than in the model. A gate checks each request before inference: you decide which prompts reach an abliterated model, which go to a standard model with its refusal behaviour intact, and which are dropped.
Gated model
model: "deepseek/deepseek-v4.1-flash-CUSTOM-ID"
Decision model
Which category does this prompt fall into?
Routes
allowed→ deepseek/deepseek-v4.1-flash-ultrafast
sensitive→ deepseek/deepseek-v4.1-flash-abliterated
prohibited→ drop · 403 Forbidden