The New York Times APIs for AI Agents
MediaContent DeliveryData TransformationOfficial Vendor DocumentsAPI keyAgent Ready
For Agents
APIs11 in catalogue
Endpoints26 indexed
AuthAPI key — 1 credential for all 11 APIs
ProvenanceOfficial OpenAPI documents
Read New York Times journalism programmatically: search the full article archive, pull bestseller and movie-review lists, track the most-shared stories, and follow a real-time newswire across 11 APIs with one key.
The Times exposes its newsroom as data, not just a website. Where a generic news API returns an undifferentiated feed, these return the same editorially curated lists, tags, and reviews the Times publishes itself. One developer key covers all 11 APIs, so an agent moves from search to archive to tags without re-authenticating.
Use for: New York Times editorial content and its metadata
Not supported: Subscriptions, Account billing, Payments, Ad buying
Credentials: Every New York Times API uses one developer key, passed as the api-key query parameter. You create the key once in the developer portal and enable each API on it. The same key works across all 11 APIs.
All 11 New York Times OpenAPI documents are vendor-official and indexed by Jentic, kept validated and agent-ready.
The New York Times publishes a family of read-only APIs over its journalism and its editorial metadata. An agent can search the article archive back to 1851, pull current bestseller and movie-review lists, see which stories readers are sharing, and follow a live wire of newly published articles. Every API is read-only and shares one developer key. The specifications are the Times's own.
The New York Times API Catalog
11 APIs across 2 product groups. All share one credential.
Media8
Books APILook up NYT Best Sellers rankings, list metadata, and book reviews for any title or author across more than 50 list categories.~6 endpointsCommunity APIRead NYT user comments by article URL, by user, by date, or as a recent feed across the site.~4 endpointsMost Popular APIGet the most-emailed, most-shared, and most-viewed NYT articles by section over the last 1, 7, or 30 days.~3 endpointsMovie Reviews APISearch NYT movie reviews by keyword, filter Critics' Picks, and look up NYT film critic profiles.~3 endpointsTimes Newswire APIStream the latest NYT and AP article URLs and metadata as soon as they are published, filterable by source and section.~3 endpointsArchive APIRetrieve a complete month of New York Times article metadata going back to 1851 from a single year/month endpoint, authenticated with an API key in the query string.~1 endpointArticle Search APIRun keyword and filter queries across NYT articles from 1851 to today and return headline, abstract, lead paragraph, and metadata fields, authenticated with an API key in the query string.~1 endpointTop Stories APIGet the editor-curated NYT articles from any section front, including home, world, business, technology, opinion, and arts.~1 endpoint
Data Enrichment3
Semantic APIResolve people, organizations, descriptors, and other named entities against the NYT controlled vocabulary and return linked-data records.~2 endpointsGeographic APIResolve place names against the NYT geographic controlled vocabulary and return linked location data with coordinates and article references.~1 endpointTimesTags APIGet autocomplete-style tag suggestions from the NYT controlled vocabulary as a user types a partial query.~1 endpoint
Which New York Times API should I use?
| I want to... | Use |
|---|---|
| Find specific articles by keyword, date, or filter | Article Search API |
| Pull historical article metadata in bulk for a whole month | Archive API |
| See what readers are reading right now | Most Popular API |
| Follow the live feed of newly published articles | Times Newswire API |
| Get the current curated headlines by section | Top Stories API |
| Get bestseller lists and book reviews | Books API |
Install Jentic One Beta
Connect the New York Times APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the New York Times APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnytimes.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnytimes.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “search New York Times articles”.
What AI Agents Can Do with The New York Times
Each workflow spans multiple New York Times APIs. Jentic routes each operation to the right API automatically.
Morning editorial briefing
Build a morning brief that pairs the curated front page with what readers are actually reading and the latest wire. The agent reads Top Stories for the editor-picked headlines, Most Popular for the most-emailed and most-viewed pieces of the day, and the Times Newswire for articles published in the last hour. The result is one digest that reflects both editorial judgment and reader behavior.
Example prompt:
Fetch the 'home' Top Stories section, the most emailed articles for the last day, and the latest Newswire items, then assemble a 10-item briefing grouped by section.
APIs used
Top Stories API + Most Popular API + Times Newswire API
Research a topic across the Times corpus
Research how the Times has covered a topic over time. The agent searches current and recent coverage with Article Search, pulls month-by-month metadata from the Archive for the historical record, and resolves the people, places, and organizations involved through the Semantic API. Together they turn one query into a sourced timeline with tagged entities.
Example prompt:
Search Article Search for 'climate policy' in 2024, pull the Archive metadata for the three months with the most hits, and resolve the top three tagged people via the Semantic API.
APIs used
Article Search API + Archive API + Semantic API
Culture recommendations
Recommend what to read and watch from Times editorial sources. The agent pulls the current bestseller lists from the Books API and cross-references critics' picks from the Movie Reviews API, so each recommendation cites the Times rather than a generic rating. Useful for a culture concierge or a weekly newsletter agent.
Example prompt:
Get this week's 'hardcover-fiction' bestseller list and the latest critics' picks, then return five paired book-and-film recommendations.
APIs used
Books API + Movie Reviews API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
You create one New York Times developer key, enable the Times APIs you want on it, and register it once with Jentic. From then on an agent reaches every enabled Times API through the same search, load, and execute calls, without per-API wiring.
Permission scoping
You decide which Times APIs the key can reach by enabling them in the developer portal, and which operations your agent is allowed to call through Jentic, so a research agent can be limited to read-only article search without touching anything else.
Credential isolation
Your single New York Times developer key is stored encrypted by your own Jentic One instance and injected at execution time. The agent receives results, never the raw key, and the one key covers all 11 Times APIs.
Intent-based discovery
An agent searches by intent, for example 'find the most emailed articles', and Jentic returns the matching operation from across the 11 Times APIs with its input schema, so the agent calls the right API without knowing which one it is.
FAQs
Specific to using The New York Times APIs through Jentic.
Can AI agents use New York Times APIs?
Yes. All 11 New York Times APIs have OpenAPI specifications in the Jentic API Directory, so an agent can discover and call them by intent. Through Jentic the agent searches for an operation, loads its schema, and executes, without reading the Times documentation first. Install Jentic One (self-hosted) from https://github.com/jentic/jentic-one to get started.
Do I need a separate key for each New York Times API?
No. The Times uses one developer key across all of its APIs. You create the key once and enable each API on it. Through Jentic the key is stored encrypted and injected at execution time, so it never enters the agent's context.
Does The New York Times publish OpenAPI specs?
The specifications in the Jentic API Directory for the Times APIs are vendor-official, sourced from the Times developer portal. The operations, parameters, and responses match what the Times documents itself.
How do I connect my agent to the New York Times APIs?
Install Jentic One on your own infrastructure from its GitHub repo, register your New York Times developer key with it once, and add the Times APIs from the Jentic API Directory. Your agent then searches by intent, for example 'search New York Times articles', and Jentic returns the matching operation across the Times APIs with its input schema.
Which New York Times API should I use to find articles?
Use Article Search for keyword and filter queries over current and recent coverage, the Archive API for bulk month-by-month metadata, and the Times Newswire for articles as they are published. Most Popular returns what readers are reading rather than a search.
What can I build by combining New York Times APIs?
Common patterns pair editorial and behavioral signals: a morning briefing from Top Stories, Most Popular, and the Newswire, or a research timeline from Article Search, the Archive, and the Semantic API. One key covers every API a workflow touches.
If you need a different Media vendor
Both are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.