September 2026
API requests·$0.01 per unit·All times UTC
Recorded checks
Inspect the recorded requests and responses
← Back to the example · Current API record, read only. Refresh reads the latest saved state.
A complete usage record, under pressure.
Step through delayed delivery, retries, late usage, and an interrupted adjustment. Each step records its actual checks.
Inspect the ledger & snapshot derivation
Event ledger
Load three sample usage events, then close the period to preserve its first snapshot.
How to read this record
Cutoff and time. Classification is fixed when a report is accepted. “Accepted at” is server time sampled before acceptance finishes; it does not establish the exact save time or event order.
Evidence and completeness. The ledger is authoritative for accepted reports. MeterProof does not verify whether the source reported all usage.
Live view and preserved results. Live values can reflect different reads. Pending means usage outside the latest snapshot shown above. Preserved snapshots stay unchanged. Automatic projection alerts and cloud recovery are not implemented.
Operator responsibility. An operator triggers close and adjustment. The demo does not enforce roles or approvals. Usage adjustments do not create or change invoices or payments.
What the evidence covers
Recorded on AWS. Basic acceptance → close → late usage → adjustment, duplicate retries, and DynamoDB Streams processing receipts. AWS verification · Recorded API evidence
Exercised locally. Delayed delivery at close, concurrent arrivals, and interruption/recovery are covered by local scenarios and tests. They are not a live AWS failure demonstration. Local scenario evidence · Concurrency tests · Recovery tests