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

# Rotten Tomatoes

Test our API services using I/O Docs. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically access Rotten Tomatoes resources. Covers 18 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Access Rotten Tomatoes resources via REST API
- Manage developer tools data programmatically
- Integrate Rotten Tomatoes into automated workflows
- Query and filter Rotten Tomatoes records by parameters
- Monitor Rotten Tomatoes operational status and events

## Use cases

### Developer Tools Operations

The API provides 18 endpoints for developer tools operations.

Example prompt: Execute a primary operation against the Rotten Tomatoes

### Data Retrieval and Monitoring

Query Rotten Tomatoes resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Rotten Tomatoes endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Rotten Tomatoes 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 'rotten tomatoes', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **Movie Lists** — Operations related to Movie Lists
- **DVD Lists** — Operations related to DVD Lists
- **Detailed Info** — Operations related to Detailed Info
- **Search** — Operations related to Search
- **Top Level Lists** — Operations related to Top Level Lists

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/rottentomatoes.com/rottentomatoes/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Rotten Tomatoes by hand means appending your apikey query parameter to every request and handling the request plumbing yourself. Through Jentic you install once, import Rotten Tomatoes from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Rotten Tomatoes takes its search and lookup terms in the request, so limit the agent to the operations it needs, such as searching movies or fetching box-office lists. You choose which operations it may call, and it can run only those.
- **Credential handling:** Your Rotten Tomatoes 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 for a movie' or 'get current box-office movies', and Jentic returns the matching Rotten Tomatoes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Rotten Tomatoes use?

The Rotten Tomatoes 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.

### What are the rate limits for the Rotten Tomatoes?

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 use rotten tomatoes through Jentic?

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

### How many endpoints does the Rotten Tomatoes have?

The Rotten Tomatoes exposes 18 endpoints covering movie lists, dvd lists, detailed info operations.

### Does the Rotten Tomatoes support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Rotten Tomatoes operations and credentials the agent may use. You can allow only the operations it actually needs, such as searching movies or fetching box-office and movie lists, while withholding others like DVD lists or detailed info lookups. The API key is stored once by your instance and injected at execution time, so the agent can call only the operations you have permitted.
