Publishable keys

Expose finished artifacts to the public safely — without ever sharing your API secret.

What they’re for

Sometimes you want a browser, a player, or a third party to fetch an artifact — a synthesized audio file or a subtitle track — without authenticating as you. A publishable key (prefixed pk_) grants scoped, read-only public access to a project’s artifacts.

Publishable, not secret

Unlike an API key, a publishable key is meant to be visible (e.g. in a web player). It can only read the artifacts it’s scoped to — it cannot create jobs, spend credits, or touch the rest of your account.

Managing keys

Each key is scoped to a project and shows its prefix.
Toggle a key’s status or revoke it at any time.
Last-used time is tracked so you can spot stale keys.

Via the API

Publishable keys authenticate public artifact requests. See the API reference for how to fetch artifacts with a publishable key, and Integrations for where this fits in the official plugins.