# API key scopes

Scopes authorize operations; they do not waive wallet, account or workflow eligibility.
Keep customer API keys in your server. The console uses its own managed credential.

| Workflow | Required scopes |
| --- | --- |
| Single title | match; read for saved results |
| Market research | research; read for saved results |
| Content generation | content; read for saved results; match if creating a title result first |
| catalog_local_v1 | match or batch for submission, acceptance, cancellation and payment retry; read for status/results |
| Recipes | Scopes required by every endpoint the recipe calls, plus read for saved results |

Catalog actions need a bound shared wallet. Legacy title-analysis batches and
group routes have different restrictions; catalog access does not enable those
routes for wallet accounts. New customer keys normally include match, read,
research and content. Check the scopes displayed on your actual key.

Read the [catalog workflow](/docs/catalog-workflow) before accepting paid work.
Review [recipe steps](/recipes) before choosing scopes or estimating their total cost.
