> 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/introduction.md).

# Introduction

The Rad TV API uses a multi-layered authentication system. Almost all operations require a valid Bearer token.

## Summary

| Mechanism   | Use case                                                                                   |
| ----------- | ------------------------------------------------------------------------------------------ |
| **JWT**     | User sessions (e.g. from Rad web/mobile login).                                            |
| **API key** | Programmatic and MCP access; generated from a JWT                                          |
| **DID**     | Canonical public identifier for channels and content (e.g. `did:rad.live:channel/<uuid>`). |

## Bearer token

Send the token on every request:

```
Authorization: Bearer <jwt-or-api-key>
```

* **GraphQL** — Include this header on `POST /graphql`. Queries and mutations marked with `@auth` require it.
* **MCP** — Required for `POST /mcp` (initialize, list tools, call tools).
* **Ingestion** — `POST /ingestion/:id` requires an API key (Bearer).

Without a valid Bearer token, protected operations return 401.

## Public operations (no auth)

Only these do **not** require authentication:

* `ratings(limit, start)` — Content ratings (e.g. MPAA, TV).
* `genres(limit, start)` — Content genres.

All other GraphQL operations and MCP tool calls require Bearer auth.


---

# 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/introduction.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.