> ## 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.

# Migration Guides

> Plan upgrades while the public API contract evolves.

## Pre-launch draft to v1

The current contract is a pre-launch draft. Do not treat internal Staging behavior, private control operations, worker bindings, database tables, or repository planning files as customer API surface.

Before moving a client to the approved Production release:

1. Regenerate or revalidate the client against the published OpenAPI contract.
2. Use `https://api.tempmaillab.com` only after public launch is announced.
3. Create a Production key in the dashboard; internal Staging keys are never customer credentials.
4. Confirm the key has the least scopes required by the workload.
5. Persist one idempotency key per logical email creation.
6. Bound message-list retries and honor `429` plus `Retry-After`.
7. Enforce the documented 30-day reservation and 15-minute content lifetimes.

## Future changes

Additive schema fields may appear within a compatible version. Clients should ignore unknown response fields while continuing to validate required fields they use. Breaking resource or semantic changes require a new versioned contract and a dedicated guide here.

No official SDK is published for the MVP. Use the OpenAPI contract, generated examples, or the maintained Postman collection rather than depending on an undocumented client library.