[santoshkumarradha]

Local and custom model endpoints could finish calls without token usage, leaving gaps in usage accounting. This improves compatible-provider handling with requested streaming receipts and clearly separated estimates when measured counts are unavailable.

• Request streamed usage, with a narrowly matched fallback for older APIs that reject the option.
• Preserve reported zeroes, partial counts, total-only receipts and native input/output aliases.
• Estimate missing text components across providers, including observed tool definitions, tool calls and visible reasoning. Mark interrupted output as partial; leave media and unseen work unknown.
• Keep estimates separate from measured counts and billing. A hashed receipt key lets later provider measurements replace estimates in analytics without adding both.
• Cover raw streaming calls as well as normal chat/task calls, preserve Ollama connection identity, and document the contract and receipt-aware PostHog query.

Companion: https://github.com/Agent-Field/website-open-infra/pull/82. Deploy that relay change first, then release this client change. Existing measured-only charts remain valid.

Validation: focused provider/config/accounting regressions, privacy/allowlist and disclosure checks, the exact shared client-to-relay fixture, a 50-event body-limit check, production build, vet, and formatting pass. The companion relay's 35 route tests pass with PostHog mocked. No synthetic production events were sent.

The broad local test gate was stopped by automatic approval review when it attempted an OpenRouter request with an unestablished payload. Targeted mock-based checks and build/vet completed; CI remains the full changed-package check.

[AbirAbbas]

Took this over to merge-ready. Four commits on top of Santosh's, each with tests named for the behaviour they prove:

• d506b8c — the red: stream_options went on every streamed request, including the default OpenRouter road. It now goes only to connected services, following the actual attempt's road, and the byte-for-byte wire law passes unedited. A service refusing the option with 422 failed a call dev answered; an explicit refusal on 400/422 now retries once and is remembered per endpoint, while an unrelated 400/422 keeps dev's exact error and request count. Ollama 0.9.0 picks completion ids from a range of 999, so the receipt key collapsed different answers into one event id with different counts; the key now includes the physical attempt.
• 78448c0 — UsageReceipt derives the status from the counts it emits, never turns an unsafe or negative count into a measured zero, and emits estimates only with a receipt, so every shape it can produce passes the relay's validator. The shared fixture grew to 24 events (relay copy in website-open-infra Onboarding asks for spend limits (daily, per plan, per task, standing) with 'no limit' as a first-class option #83).
• 0928ce1 — the generation id is canonicalised the same way for the estimate and the late receipt; repeated tool names count once; opaque reasoning sidecars no longer grow a text estimate; a role-only frame before a cut observes nothing; the stream-options repair composes with the existing repairs in either order, bounded once per kind; refusal matching must qualify the option itself; a late receipt keeps token presence (cost-only adds no token event; one count stays partial). The unmetered direct-service answer keeps dev's no-lookup behaviour, because that lookup would carry the direct vendor's key to the overflow host.
• 9445d02 — docs, manual and change entry match the code, including the native input_tokens/output_tokens aliases now landing as measured counts (dev recorded 0/0).

Verified: CI green on this head; make pr-ready green; the real binary against a stub matrix (reported, none, zeros, total-only, one-sided, 400/422 refusals, unrelated 400, cut, reasoning, tool calls, repeated names, both repair orders, false-positive refusal, native cache aliases) and a local Ollama 0.9.0, compared against a dev build; every scenario that answered on dev still answers. 493 captured client events replayed through the relay route handler from website-open-infra #82: 0 dropped. No prompt, path, model, endpoint or key in any captured body.

Merge order stays as Santosh set it: this goes in once the relay deploy from #82 is confirmed live.

[AbirAbbas]

Verified; see the comment above. Merge waits on the relay deploy confirmation.