/healthz, /readyz, and POST /v1/keys) require an API key.
Passing the key
Two methods are supported:- Header (recommended)
- Query parameter
Key format
API keys use the prefixpn_live_ followed by a random string. Legacy keys with qm_live_ prefix are also accepted.
Account-level usage
All active API keys owned by the same account contribute to one shared monthly usage total. Creating, renaming, rotating, or using multiple keys does not create separate allowances or reset usage. The usage dashboard is authenticated by your signed-in account; you do not submit a raw API key to view it. See Monthly usage allowances for the exact meters and included plan capacity.Generating a key
Key generation is rate limited to 1 per IP per day.
Security
- API keys are SHA-256 hashed before storage. The raw key is never persisted.
- All traffic should use HTTPS in production.
- Rotate keys by generating a new one and decommissioning the old one.

