Browse managed policies in the Requesty Console.
How It Works
1
Requesty maintains the policy
Requesty curates the model chain behind each managed policy and keeps it up to date as providers change. You never need to edit anything.
2
You reference the policy by name
Use the policy name as-is as the
model in your request. Unlike custom policies, managed policies do not use the policy/ prefix.3
The router does the rest
Requests are routed across the models in the policy. Models that are not on your approved list are skipped automatically.
Benefits
Zero Setup
Ready-made policies with no configuration required.
Maintained by Requesty
We update the model chain as providers evolve, so you always route on current best practice.
High Availability
Multiple providers behind one name means fewer failed requests.
Override When Needed
Create a custom policy with the same name and yours takes precedence.
Using a Managed Policy
1
Find a Managed Policy
Go to the Managed tab on the Routing Policies page. Each row shows the policy name, its copyable model ID, and the models it routes across. Click a policy to see its full model chain.
2
Use the Policy in Your Code
Reference the policy name directly as the
model. No policy/ prefix:Managed vs Custom Policies
If your organization has a custom policy with the same name as a managed policy, your custom policy takes precedence.
Good to Know
- Models in a managed policy that are not on your organization’s approved model list are skipped automatically. They appear grayed out with a warning in the Console.
- Managed policies work with the same analytics, cost tracking, and logs as any other request.
- Want full control over strategy and models? Create your own Fallback, Load Balancing, or Latency policy instead.