Check the current provider rate
Jev may be available through more than one provider surface. Treat each provider page as the source of truth for its current model ID, billing unit, limits, and included usage because those details can change.
Measure decisions, not requests
A cheap request can still be expensive if many outputs are uncertain, invalid, or retried. Track input usage, latency, confidence, error rate, and the percentage of results that enter fallback.
Include the human review path
If low-confidence cases go to a reviewer, that work belongs in the unit economics. A useful comparison reports cost per accepted automated decision and cost per reviewed decision separately.
Do not estimate missing usage fields
When a provider omits usage or pricing data, mark it unavailable and reconcile with provider billing. Invented precision makes model comparisons less trustworthy.