Skip to main content
Stop guessing which model is best for your use case — race them on your actual prompt:
POST /api/v1/compare
The response is a ranked leaderboard:
cost_cents on each result is that model’s real metered charge for its actual response length in this race — not a fixed per-model number, so re-running the same compare can shift these slightly even with the same models.
Only the top-level winner object carries a display name (resolved from the model catalog) — individual entries in results[] and failed[] identify the model by its model slug only. Each result also carries tokens (prompt / completion / total), success, and quality.flags / quality.suggested_retry. Top level adds failed[], ranked_by, models_compared, succeeded, total_cost_cents, balance, and compared_at.

Parameters

Billing: the sum of each successful model’s real metered token usage — a 4-model compare here cost $0.0244. Failed models aren’t charged, and the whole request is rejected up front if your balance can’t cover the estimated maximum.

The workflow it’s built for

1

Race on real prompts

Take 5 prompts from your actual workload, run them through /compare with the models you’re considering.
2

Read the summary, not the vibes

summary.best_value is the quality-per-dollar pick; winner is the balanced pick.
3

Commit and monitor

Hard-code the winner. Re-run the same compare monthly — model updates shift results.
The same idea exists for images — agents race image models with compare_models on the MCP server.