Simulate squad classifier routing
Dry-run the squad’s classifier routing for a message without persisting or delivering anything: the classifier agent runs under the same model the production router would use and returns which of the squad’s labels it selects, so you can verify label coverage before deploying. Body: { "message": string } (1–8000 chars, required). Owner, admin, or developer role required.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Response
The routing simulation result — the echoed squad_id, message, classifier_model, the predicted label and reasoning — in the standard { data, meta } envelope.