Key facts
| Router model | model="plugsky-fusion" applies a strategy per client workspace (live) |
| Scoping | Strategies and rules per workspace or API key, one project per client |
| Defaults | cost_saver or balanced for routine volume; max_quality for premium queues |
| Cost model | Flat self-serve plans; no per-token charges, fair-use RPM per tier |
| White-label | Deliver routing-driven services under your own brand |
| Observability | Model, strategy and rule logged per request; tokens returned in responses |
| Residency | Pin each client workspace to the region their contract requires |
| Roadmap | Classifier routing /v1/plugsky/route (model=auto) is coming soon |
TL;DR
- Template one routing policy and stamp it across client workspaces.
- Keep routine traffic on cheap-first strategies and escalate deliberately.
- Reserve premium strategies for clients who pay for premium outcomes.
- Use per-client logs for margin reviews and client reporting.
- Pin each workspace to its contracted region without changing code.
How it works, step by step
- Design a small set of strategy templates: economy, standard and premium support.
- Create each client workspace with its template attached and keys scoped to that project.
- Add escalation rules only for markers you trust — ticket complexity, language or tool use.
- Track routing distribution per client monthly to spot templates that cost more than they should.
- Publish routing summaries in your portal to show where quality investment went.
- Adjust one template at a time and roll it out to matching clients.
Try it yourself
Open the AI workload router simulator →
Strategy templates per client tier
MSPs thrive on repeatability. Instead of tuning models per client, define two or three routing templates — economy, standard, premium — and attach one to each client workspace. Economy runs cost_saver with escalation on genuinely hard prompts; standard runs balanced; premium runs max_quality for the queues that justify it.
Because strategies can be scoped per workspace or API key, a change to a template propagates through a review-and-apply process, not a code deploy. That is the operational difference between managing a platform and firefighting a stack.
Escalation that protects margin
Margin is decided at the escalation boundary. If every ticket can reach a frontier model, premium cost leaks into economy contracts. Write rules with clear markers: tickets that contain error codes or tool calls escalate; FAQs and status checks stay cheap.
- Measure: the decision log shows escalation rates per client, so a mis-tuned threshold is visible before it becomes a margin problem.
- Cap: where contracts require it, pin a fixed model for a client to bound outcomes and cost.
- Flat pricing: no per-token charges means more traffic does not mechanically shrink gross margin.
Client reporting without leaking your economics
Clients want evidence their service is run well. Routing logs give you the story in neutral terms: most requests answered instantly on efficient models, complex cases escalated for better outcomes, and residency honoured. Token telemetry returns in every response for your internal reviews, even though it does not drive billing.
Keep the platform white-label so client-facing material carries your brand, and keep region pinning per workspace so a client expanding into a new jurisdiction gets the right deployment without a re-platforming project.
Honest comparison
| Concern | Plugsky routing | Per-client model stacks | Reselling per-token APIs |
|---|---|---|---|
| Per-client policy | Strategy templates per workspace | Duplicated configuration | Account-level settings |
| Escalation control | Ordered rules with clear markers | Manual | Limited |
| Margin visibility | Routing logs and token telemetry | Custom reporting | Provider invoices |
| White-label | Full brand control | Full | Provider branding |
| Ops load | Template changes | Per-client maintenance | Billing reconciliation |
Frequently asked questions
How do we give each client a different policy?
Create one workspace per client and attach a strategy template — economy, standard or premium. Strategies can be scoped per workspace or key.
How do we stop premium models leaking into cheap contracts?
Escalate only on reliable markers and review the decision log monthly. If a client must be bounded, pin a fixed model for their keys.
Does routing raise our costs as clients grow?
Self-serve plans are flat with unlimited fair-use usage and no per-token charges, so growth changes request rate, not per-token spend.
Can each client have its own region?
Yes. Pin each workspace to the contracted region, or use VPC, on-prem and air-gapped deployment for stricter contracts.
Can we white-label the routing layer?
Yes. The routing behaviour is internal to your delivery; clients see your portal and your brand.
What do we show clients about routing?
Use the decision log for internal reviews and share neutral summaries — efficient handling, escalation on hard cases, residency compliance.
How quickly can we onboard a client?
Attach a template, create scoped keys, import their content and point their channel at your service — typically the same day.