RoutingComing soon

Virtual model aliases

One stable model name in your code, pointed at any model or provider behind the scenes.

Coming soonChange models without code changesOrdered and weighted targets

What is Virtual model aliases?

A virtual model alias is a custom model name that maps to one or more real models and providers. Your application calls the alias, and the gateway picks a target using a routing rule such as priority order or weights. You change what the alias points to in the dashboard, with no code change or redeploy.

Hard-coding a model name spreads a model choice across every service that calls it. A virtual model alias moves that choice into one place. Your code calls a name such as support-chat, and the gateway decides which model answers.

Aliases are a common way to run gradual rollouts and A/B tests. Give a new model a small share of traffic, compare results in spend and request logs, then raise the share. This page describes a feature that is still in development, so details can change before release.

Key features

What this feature does for your requests.

  • A stable alias name used in the model field
  • Ordered targets for priority and fallback behaviour
  • Weighted targets for gradual rollouts and A/B tests
  • Targets changed from the dashboard without an application redeploy
  • Results visible per target in spend and request logs

How it works

4 steps, from setup to the first request.

  1. 01

    Create an alias

    Name it for the job it does, such as support-chat.

  2. 02

    Add targets

    Choose the models and providers behind it, with an order or weights.

  3. 03

    Call the alias

    Send the alias in the model field, the same way you send a model name.

  4. 04

    Change targets anytime

    Edit the targets in the dashboard. The next request uses the new setup.

Is it the right fit?

Specific situations where this feature helps, and where it does not.

Good fit if

  • Several services call the same model and you want to change it in one place
  • You plan gradual rollouts of a new model with a traffic split
  • Someone outside engineering should be able to change the model behind a feature

Not a good fit if

  • You use one model and do not expect to change it
  • Compliance or testing requires each caller to name a specific model
  • You cannot yet check output quality on a new target before shifting traffic to it

Virtual model aliases FAQs

Common questions about Virtual model aliases.

Route every AI request through SPRO.

One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.

Talk to sales