> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tempmaillab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat docs/openapi.yaml as the normative public API contract.
> Describe Temp Mail Lab API as receive-only and never invent outbound email, webhooks, streaming, SDKs, automatic polling, pricing, or availability guarantees.
> Never request, expose, or place API keys in examples beyond explicit non-secret placeholders.

# Usage and Quotas

> Read authoritative allowance and understand which requests are charged.

Premium includes 10,000 API requests per UTC calendar month. The allowance window starts at `00:00:00Z` on the first day of the month and resets at `00:00:00Z` on the first day of the next month, independently of whether Premium was purchased weekly, monthly, or through a one-time payment.

Call `GET /v1/usage` for the authenticated account's current allowance window. The usage endpoint itself does not consume monthly allowance.

```bash theme={null}
curl --fail-with-body \
  --header "Authorization: Bearer $TML_API_KEY" \
  "$TML_API_BASE/v1/usage"
```

The response reports the period start and reset time, monthly allowance, used and remaining requests, and any remaining additional-request allowance.

## Accounting rules

* Completed authenticated public operations are charged according to the OpenAPI contract.
* A `304` is charged because the service authenticated and checked the resource.
* An exact successful create-email idempotency replay is not charged again.
* `GET /v1/usage` is not charged.
* `401`, `403`, `429`, and service `5xx` responses are not charged.
* Authenticated processed `400`, `404`, `409`, and `422` responses are charged.
* Inbound SMTP admission is independent from public API usage.

`RateLimit-Limit`, `RateLimit-Remaining`, and `RateLimit-Reset` mirror the authoritative request allowance on applicable responses. A renewal within the same UTC month does not reset usage. Dashboard entitlement and the live API response remain authoritative for the current window and any separately purchased request pack.