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

Do not use JWTs for long-lived scripts or MCP from IDEs; use an API key instead.

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

API keys are intended for programmatic/long-lived use; JWTs are for interactive user sessions.

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.