Skip to main content
One complex instruction branching into parallel reasoning paths and reconciling into one result
Multipath uses a separate SERV reasoning transformation for instructions with several branches, exceptions, or competing rules. It keeps the source prompt as the task context while making the procedural logic explicit before the model runs.

Enable Multipath

Add -serv-multipath to a supported base model ID. The suffix is a model feature, not an application tool, so you do not add a function definition or implement a handler for it.
SERV removes the feature suffix before routing to the upstream provider. Use a real base model from the model catalog, then append -serv-multipath exactly once.

Combine Multipath with Kronos

For complex branching rules that also need semantic auditing, combine the features in one suffix:
The order does not change the selected features. -serv-multipath-kronos is also recognized, but use one consistent spelling across your integration.

When to use it

Use Multipath for decision trees, policy matrices, routing rules, and instructions where different conditions lead to different outcomes. For a short, linear system prompt, start with the standard SERV model and measure before adding the feature. Multipath does not execute branches or authorize actions in your application. Keep business rules, permissions, and side-effect checks in your code. The transformation adds SERV prompt-generation work and may increase latency and cost. Prompt caching can reuse a matching Multipath transformation; the upstream model still runs for every request. See Monitor usage and billing.