Compare routes per task
- Company facts extraction (S1): Best go-to: gaents/deepseek (correct share of filled fields 90.5%, recall (filled where the key has a value) 91.6%; $0.561 cash per 1,000 correct fields): inside the interval of the top callable route gaents/claude-haiku (91.7%, interval 90.3%-93.0%; $0.6134 capacity per 1,000 correct fields) on every measured quality column. 0.91 times the incumbent's cost per correct output. The cheaper gaents/gpt-oss ($0.1469 cash per 1,000 correct fields) does not qualify: correct share of filled fields 87.2% is below gaents/claude-haiku's interval 90.3%-93.0%.
- Industry placement (family level): Best go-to: gaents/qwen-flash (family precision 0.77, family recall 0.72; $1.204 cash per 1,000 correct family placements): inside the interval of the top callable route gaents/claude-haiku (0.83, interval 0.77-0.88; its cost: not recomputable at the corrected Haiku price: Pixel's race logged the CLI's total_cost_usd per call (its Haiku call log, usd_notional) and no token counts) on every measured quality column. The cheaper gaents/deepseek ($1.174 cash per 1,000 correct family placements) does not qualify: family precision 0.66 is below gaents/claude-haiku's interval 0.77-0.88; family recall 0.59 is below gaents/claude-haiku's interval 0.70-0.82.
- Coding tasks (agent with a harness): Best go-to: gaents/claude-opus (incumbent stays): the top callable route (86%, interval 72%-93%; $0.9086 capacity per passing run). The cheaper gaents/glm-flash ($0.0703 cash per passing run) does not qualify: mergeable as-is (blind review of passing diffs) 44% is below gaents/claude-opus's interval 70%-100%.
The go-to rule is a setting, models.go_to_rule (agent-chosen, unruled; Adam sets): Start from the top-scoring route you can call as one gaents alias (the incumbent). A cheaper callable route becomes the go-to only if, on EVERY measured quality column of the task, its score is inside or above the incumbent's 95% interval. If a cheaper route falls below on any column, the incumbent stays and the line says which column. Cost per correct output is ranked on cash plus capacity at list price; the two are shown in separate columns. Cost basis (models.cost_basis_rule): Cash (billed by the provider) and capacity (API-equivalent list price of a Claude subscription login, not cash) are separate columns and never added for display. Only the go-to ranking adds them, because gaents prices both from list price.