Releases
Antaeus v0.6.0 adds provider token accounting
Opt-in Drex usage reporting preserves token accounting across retries and fallback while keeping unknown usage distinct from zero.
Antaeus v0.6.0 adds opt-in provider token accounting for Drex evaluations. Applications can inspect consumption across retries, escalation, and fallback without interpreting unknown usage as zero.
Opt in through the evaluator profile
Select System One adapter 0.4.0 to receive the separate io.antaeus.usage decision extension. Accounting records align with execution attempts and distinguish reported counters from unavailable or invalid usage.
Usage can remain visible after an invalid answer, failed attempt, or confidence-routing step. It does not affect policy reduction or assign customer charges. Other System One providers report unavailable usage until their accounting contracts are verified.
Existing adapter versions keep their behavior. The execution trace and version-1 WebAssembly host interface retain their existing shapes. Go callers must register the new usage identity explicitly to opt in and should follow the migration notes for the added result field.
Read the v0.6.0 release notes, provider usage contract, and System One setup guide. Visit Open source for current installation options.
Questions and answers
Does Antaeus provider token accounting change policy decisions?
No. The opt-in io.antaeus.usage extension reports provider consumption separately from policy reduction. Accounting does not change the policy outcome.
Does unavailable provider usage mean zero tokens?
No. Antaeus keeps unavailable or invalid usage distinct from reported counters. Applications must preserve that distinction rather than treat missing accounting as zero consumption.