> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Keys

> How pipelines and scripts authenticate with Earnie, how to create and scope a key, and why each automation consumer should have its own.

## Why API Keys

Pipelines and scripts authenticate with an API key rather than a person's account.

## Creating a Key

Create one under **Settings → API Keys**. Each key is:

* **Scoped to a project**
* Given an **expiry**
* **Read-only**, if that's all it needs

<Note>
  The key is shown once, copy it then, because it cannot be retrieved
  afterwards.
</Note>

## Revoking a Key

Revoking a key takes effect immediately.

<Note>
  **Give each consumer its own key.** One key per pipeline, named for that
  pipeline. When something needs to be revoked you revoke exactly one thing,
  and the audit log tells you which automation did what.
</Note>

## What's Next

That covers the full walkthrough, from an empty workspace to a governed codebase. From here, revisit the [Introduction](/en/latest/earnie/introduction) for the concepts, or jump back into any step of the workflow.