Batch routing demo
Walk through a realistic BatchRouter job without signing in, spending credits, or hitting a live provider. The data is local, but the lifecycle is the real one: manifest, quote, route, dispatch, verify, and deliver artifacts.
Selected workloadOpsMorning support digest
Quote total$1.8436 routable work units in this run
Expected runtime~11 minutes36 queued items
Providers2OpenAI, OpenRouter compete for acceptable work
Demo scenarios
Morning support digest
Summarize yesterday's ticket export into a leadership brief, with a separate red-flag file for the incidents that still need a human on call.
Sample manifest excerpt
{
"sla_tier": "standard",
"routing_mode": "sla_aware",
"privacy_tier": "confidential",
"allowed_regions": [
"eu",
"us"
],
"items": [
{
"customer_item_id": "support_rollup_001",
"operation": "responses",
"model": "gpt-4.1-mini",
"input": {
"input": [
{
"role": "system",
"content": "Produce an ops-ready summary with owners, risks, and confidence."
},
{
"role": "user",
"content": "Summarize ticket cluster 12 into five bullets and call out any churn risk."
}
]
}
},
{
"customer_item_id": "support_rollup_002",
"operation": "responses",
"model": "gpt-4.1-mini",
"input": {
"input": [
{
"role": "user",
"content": "Extract unresolved billing blockers from ticket cluster 14 and rank by urgency."
}
]
}
}
]
}Browser path
Use this when you want the easiest path from first touch to a real finished batch run.
API path
Use this when you already know the manifest shape and want software to wait for the finished artifact.
