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

# API Keys

> Create and manage organization API keys under Settings → Developer. Keys authenticate the Usage Push API.

API keys authenticate programmatic access to Quivly — primarily the [Usage Push API](/integrations/product-usage/api-overview). Manage them under **Settings → Developer**.

## Creating a key

1. Go to **Settings → Developer**.
2. Click create, name the key (e.g. `production-backend`), and generate it.
3. **Copy the key immediately** — treat it like a password and store it in your secrets manager.

Use it as a bearer token:

```bash theme={null}
curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://app.quivly.ai/api/v1/usage/events \
  -X POST -H "Content-Type: application/json" \
  -d '{"events":[{"external_customer_id":"cus_acme","metric_key":"api_calls","value":1500}]}'
```

Keys are organization-scoped — one key works for your whole org, with no per-key permission levels.

## Archiving a key

Archive from the same page; you'll confirm by typing the key's name. Archiving is permanent and immediately breaks any integration still using the key, so rotate consumers first.

## FAQ

<AccordionGroup>
  <Accordion title="Do API keys grant access to the MCP server?">
    No — the [MCP server](/developers/mcp-server) uses per-user OAuth sign-in, not API keys.
  </Accordion>

  <Accordion title="How do I rotate a key?">
    Create a new key, switch your integrations to it, then archive the old one.
  </Accordion>
</AccordionGroup>