Try the Rotten Tomatoes movie reviews API

- `data.render` is present for `browser_render` responses and records how many distinct review pages were loaded, how many "Load More" steps were needed, and the total time in milliseconds. It is an audit record, not a cache age. `feed_api` responses have no `render` block. - `data.reviews_api_url` is the review-list request on the Rotten Tomatoes website that corresponds to the requested page. It identifies the page; it is not necessarily the request that served the response, and it cannot be fetched by an ordinary HTTP client. - `data.source_url` is the public review page for the requested list, for example `https://www.rottentomatoes.com/m/clayface/reviews/all-critics`. - `created_at` is the review's upstream creation time in ISO 8601 (for example `2026-10-28T22:12:45.000Z`) for `feed_api` and `browser_render` responses. It is not a record of when a review became visible on the site, and it is not the display text on the page. For `public_page` responses `created_at` is only what the page prints, which for older films is a calendar date (`Mar 20, 2024`) and for a film in its first day or two is relative text such as `2 hrs ago`. - `updated_at` is set when a review was edited after it was created, and `status` is the upstream review status (normally `ACTIVE`). - `rating` and `rating_label` are the audience star rating: `rating` is the numeric value (`4.5`) and `rating_label` the upstream label (`STAR_4_5`). Critic reviews carry `original_score` instead when the critic published a score (`4/5`, `B+`). - `publication_review_url` links to the original article. Corrections and removals are not reported. - Review type values other than `critics`, `top-critics`, `audience`, and `verified-audience` are rejected before upstream IO. - Blocked requests, malformed review data, and parser drift return upstream errors.