API keys authenticate every request to the render API. Keys are workspace-scoped — a key can only render templates that belong to the workspace it was minted in.
Creating a key
- Open Account → API keys.
- Click New key, give it a label (e.g. Production server).
One key type
pxd_…— the only key type, minted on every plan. Renders are never watermarked.- Credits are the volume limit; your plan sets the request rate limit — see Rate limits.
- Keys minted before 2026-08-05 (
pxd_live_…/pxd_test_…) still work and behave identically — the prefix carries no meaning any more.
Upgrading your plan
Nothing about your key changes when you upgrade. The same key immediately gets the higher rate limit and your new credit grant — no re-minting, no redeploy.
Rotating a key
Create the new key first, deploy it, then revoke the old one. Revoked keys return 401 api_key_revoked within 60 seconds.
Revoking
Click Revoke. The key stops working within 60 seconds. In-flight renders that already authenticated complete normally.
Never ship keys to the browser
API keys grant render access to every template in your workspace and spend your credits. Store them on your server or in a serverless function — never bundle one into a frontend build.