OpenChainGraph Suite · ART-704

AI Token Spend

Monthly AI token spend and a cross-model comparison from a usage profile and a dated price table: per-model monthly cost, cost per request, the input / cached-input / cache-write / output breakdown, and a cheapest-first ranking. Prices are an input, never kernel constants: the default prices below are a dated snapshot of the official provider price pages.

AI SpendDated SnapshotInteger MicrosZero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data; use synthetic or anonymised inputs only.
Scope & reliance
Pricing date as_of is an input; the node reads no clock. A price entry applies when effective_from ≤ as_of ≤ effective_through (null bounds are open); two applicable entries for a compared model are an AMBIGUOUS_PRICE refusal, and a missing block or component price is a refusal naming the model and the component. Batch and long-context shares split each component's tokens into disjoint slices priced from the matching block (the batch block, the long-context block, or the combined batch+long-context block when the provider lists one; otherwise NO_PRICE_FOR_COMBINATION). The cost of T tokens at price P is floor(T/1e6)·P + floor((T mod 1e6)·P/1e6), overflow-safe under the validated caps (monthly tokens per component at most 10¹²; prices at most 10⁹). The estimate covers text tokens only: taxes and regional uplift, image, audio and video tokens, tool-use surcharges, tiered volume discounts, and subscription or committed-spend deals sit outside the estimate, and this node ships compute_proof_ready: ready; see the proof-status note below the results.
Usage profile, price table and comparison set
Edit any field and run. The sample prices the 2026-10-04 snapshot below at a 60%-cached usage profile across one model per provider.
Result
Priced snapshot
Proof status
This node ships compute_proof_ready: ready: ZK-proven. The shard pins a zkVM execution receipt (risc0/groth16-bn254) whose seal commits to this kernel's source digest, and the result above is hash-committed in the receipt journal and recomputable from the same inputs.
Execution Hash & §4 Artifact
SHA-256 execution hash (JCS canonical, RFC 8785):