canonical: https://jentic.com/apis/watchmode.com/watchmode

# Watchmode API

Watchmode API for finding streaming availability of movies and TV shows across platforms. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically search titles, get title details. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Search titles
- Get title details
- List all titles
- Query and filter Watchmode API records by parameters
- Monitor Watchmode API operational status and events

## Use cases

### Media and Content Operations

Use the Watchmode API to perform media operations programmatically. The API provides 8 endpoints covering core functionality including search titles, get title details, get streaming sources.

Example prompt: Call GET /search to search titles

### Automated Search Management

Automate search operations by combining multiple Watchmode API endpoints. Agents can get title details and then get streaming sources in a single workflow.

Example prompt: Call GET `/title/{id}/details` to get title details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Watchmode API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'search titles', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/search` | Search titles |
| GET | `/title/{id}/details` | Get title details |
| GET | `/title/{id}/sources` | Get streaming sources |
| GET | `/list-titles` | List all titles |
| GET | `/sources` | List streaming sources |
| GET | `/networks` | List TV networks |
| GET | `/title/{id}/cast-crew` | Get cast and crew |
| GET | `/releases` | Get new releases |

## Key resources

- **Search** — Operations related to Search
- **Titles** — Operations related to Titles
- **Sources** — Operations related to Sources
- **Releases** — Operations related to Releases

## Why Jentic

- **Setup:** Wiring the Watchmode API by hand means passing your key as the apiKey query parameter on the api.watchmode.com/v1 host and attaching it to every request yourself. Through Jentic you install once, import the Watchmode API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Watchmode API puts the title id in the URL path (`/title/{id}/details` and `/title/{id}/sources`), so a rule can pin your agent to one title. Its operations are read-only, so you choose which reads the agent may call and it can fetch title details, sources and cast data and nothing beyond that.
- **Credential handling:** Your Watchmode API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search titles' or 'get streaming sources for a title', and Jentic returns the matching Watchmode API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Watchmode API use?

The Watchmode API uses an API key passed in the `apiKey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I search titles with the Watchmode API?

Yes. Use the GET /search endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Watchmode API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I search titles through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search titles'. Jentic returns the matching Watchmode API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Watchmode API have?

The Watchmode API exposes 8 endpoints covering search, titles, sources operations.

### Can I limit what my agent is allowed to do with the Watchmode API?

Yes. Because you run Jentic One yourself, your own rules decide which Watchmode operations and credentials the agent may use. Since every operation is read-only, you can allow only the specific reads you want, such as GET /search or GET `/title/{id}/details`, and keep the rest off limits. And because the title id sits in the URL path for `/title/{id}/details`, `/title/{id}/sources` and `/title/{id}/cast-crew`, a rule can pin the agent to a single title so it fetches details, sources and cast data and nothing beyond that.