> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/rad-tv-developer-api/bearer-tokens.md).

# Bearer Tokens

All protected Rad TV API requests use the same header:

```
Authorization: Bearer <token>
```

The token can be a **JWT** (user session) or an **API key** (programmatic/MCP).

## Where to send it

| Endpoint                               | Header                            |
| -------------------------------------- | --------------------------------- |
| `POST /graphql`                        | `Authorization: Bearer <token>`   |
| `POST /mcp`, `GET /mcp`, `DELETE /mcp` | `Authorization: Bearer <token>`   |
| `POST /ingestion/:id`                  | `Authorization: Bearer <api-key>` |

## JWT tokens

JWTs are issued by the platform when a user logs in (e.g. via Rad web or mobile). Use them for:

* GraphQL requests as the logged-in user

{% hint style="warning" %}
Do not use JWTs for long-lived scripts or MCP from IDEs; use an API key instead.
{% endhint %}

## API keys

API keys are long-lived tokens generated from a JWT. Use them for:

* MCP access (Cursor, Claude, etc.)
* Scripts and automated clients
* `POST /ingestion/:id` uploads

{% hint style="info" %}
API keys are intended for programmatic/long-lived use; JWTs are for interactive user sessions.
{% endhint %}

## Invalid or missing token

If the token is missing or invalid:

* **GraphQL** — Queries/mutations with `@auth` return an error (e.g. 401 or error in `errors`).
* **MCP** — Initialize and tool calls return an error (e.g. "Authentication required. Send Authorization: Bearer .").

Only `ratings` and `genres` GraphQL queries work without a token.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rad.live/rad/rad-tv-developer-api/bearer-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.