Usage, Quotas and Audit History

What it does

Usage is counted per tenant and per API key. Quota is enforced before processing — including for batches — and every significant action is written to a hash-chained audit log that cannot be edited silently.

How it works

1. 1Quota checked before a document is accepted
2. 2Over quota → HTTP 429 with a clear code
3. 3Usage recorded per document
4. 4Audit entry appended and hash-chained

Sample result

Illustrative response shape using synthetic data.

{ "error": { "code": "quota_exceeded", "message": "Monthly quota of 1500 documents reached" } }