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

> ## Agent Instructions
> Quiver Quantitative API: base URL https://api.quiverquant.com, endpoints under /beta/. Authenticate every request with the header `Authorization: Bearer <API key>`. Keys are on https://api.quiverquant.com/dashboard/ after subscribing at https://api.quiverquant.com/pricing/.
> AI agents can use the Quiver MCP server at https://mcp.quiverquant.com/ (streamable HTTP; OAuth sign-in, or the API key as a Bearer token). Setup: https://api.quiverquant.com/docs/mcp-server.
> Each dataset needs a plan (https://api.quiverquant.com/docs/plans-and-access) and each endpoint has a per-account rate limit (https://api.quiverquant.com/docs/rate-limits).

# Authentication

> Authenticate Quiver API requests by sending your API key in the Authorization header as a Bearer token.

Send your API key in the `Authorization` header of every request:

```bash theme={null}
curl https://api.quiverquant.com/beta/live/congresstrading \
  -H "Authorization: Bearer YOUR_API_KEY"
```

`Authorization: Token YOUR_API_KEY` also works. Both forms use the same key.

## Where do I find my API key?

Your API key is on your [dashboard](https://api.quiverquant.com/dashboard/), labelled **Authorization Token**. You get it when you create an account. It only returns data once you have an active plan; choose one on the [pricing page](https://api.quiverquant.com/pricing/).

The same key works for the REST API and the [MCP server](/docs/mcp-server.md).

## How do I keep my API key safe?

Anyone with your key can use your plan and count against your rate limits.

* Store the key in an environment variable or a secrets manager, not in your source code.
* Don't put the key in client-side code such as a browser app, where users can read it. Call the Quiver API from your server instead.
* If your key is exposed, contact [info@quiverquant.com](mailto:info@quiverquant.com).

## What happens if authentication fails?

| Status | Response | Cause |
| - | - | - |
| `401` | `{"detail": "Authentication credentials were not provided."}` | The `Authorization` header is missing, or it doesn't start with `Bearer` or `Token`. |
| `401` | `{"detail": "Invalid token."}` | The key is wrong. Copy it again from your dashboard. |
| `403` | `{"detail": "Upgrade your subscription plan to access this dataset."}` | The key is valid, but your plan doesn't include this dataset, or you don't have an active plan. See [Plans and data access](/docs/plans-and-access.md). |

See [Errors](/docs/errors.md) for every status code the API returns.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.