Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs/Nytimes
Nytimes logo

Nytimes APIs

12 APIs33 Endpoints2 Categories

Categories

All12Media9Data Enrichment3

API Catalog

Books API

The New York Times Books API provides programmatic access to NYT Best Sellers lists and book reviews. Agents can retrieve current and historical best seller rankings across more than 50 list categories (hardcover fiction, nonfiction, children's, advice, graphic novels), look up an individual title's appearance history, and pull reviews written by NYT critics. Results include ISBNs, author names, publishers, weeks-on-list counts, and Amazon product URLs, making the data immediately usable for book recommendation and discovery experiences.

6 endpoints

Books API

This NYT Books spec is a third-party Konfig-sourced bundle that mirrors the NYT Books service with one extra endpoint, /lists/full-overview.json, returning the complete entries across every active Best Sellers list rather than just the top five. The 7 GET endpoints provide programmatic access to NYT Best Sellers rankings (current and historical), the catalogue of available list names, individual book ranking history by ISBN or author, and NYT critic book reviews. Responses include ISBN-13, weeks-on-list, rank-last-week, publisher, and Amazon product URLs.

7 endpoints

Community API

The New York Times Community API provides read access to comments left by registered users on NYT articles. Agents can pull recent comments site-wide, filter by article URL, retrieve a specific user's comment history, or fetch comments posted within a date range. Each comment record includes the author's display name, comment body, recommendation count, NYT pick flag, and the article URL it was posted on. The API is officially marked deprecated by NYT, but the endpoints continue to respond and remain useful for archival research and sentiment analysis on legacy NYT comment threads.

4 endpoints

Geographic API

The New York Times Geographic API extends the NYT Semantic API with a linked-data layer that resolves location concepts in the NYT controlled vocabulary against external geographic data sources. A single /query.json endpoint accepts a place name or NYT geo concept identifier and returns enriched location records with coordinates, geo facets, and references to the NYT articles tagged with that location. It is designed for agents that need to disambiguate place names mentioned in NYT coverage and link them to consistent geographic identifiers.

1 endpoints

Most Popular API

The New York Times Most Popular API returns the most-emailed, most-shared, and most-viewed NYT articles for the past 1, 7, or 30 days. Three GET endpoints take a section filter and a time-period parameter and respond with ranked article lists including title, byline, abstract, publication date, web URL, and embedded media. The API is a fast way to surface trending NYT coverage and identify the stories generating the most reader engagement.

3 endpoints

Movie Reviews API

The New York Times Movie Reviews API exposes the NYT film criticism archive through three GET endpoints. Agents can search reviews by keyword, filter by Critics' Pick status, opening date, or publication date, and look up the roster of NYT film critics with their bio and profile image. Each review record includes the film title, MPAA rating, byline, headline, summary short, link to the full review, and an opening-date flag, supporting film discovery, recommendation, and editorial integrations.

3 endpoints

NYT Archive API

The New York Times Archive API returns the complete list of NYT articles published in a given month, going back to September 1851. Each response is a month's worth of article metadata — headlines, abstracts, bylines, sections, keywords, and links — making it the canonical bulk-retrieval endpoint for NYT content. The API exposes a single GET path keyed by year and month, which is intentionally the simplest possible surface for building local mirrors of NYT metadata, training corpora, longitudinal analysis sets, and timelines.

1 endpoints

NYT Article Search API

The New York Times Article Search API exposes a single search endpoint that runs queries against NYT articles published from September 18, 1851 to today. It supports keyword queries, filter queries (Lucene-style on fields such as section, byline, and date), date ranges, sorting, and faceting, and returns headlines, abstracts, lead paragraphs, multimedia links, and other article metadata. The endpoint is well suited to building topic monitors, citation tools, research dashboards, and AI agents that need to retrieve specific articles rather than walk the full archive.

1 endpoints

Semantic API

The New York Times Semantic API exposes the NYT controlled vocabulary of people, places, organizations, descriptors, titles of works, and other named entities used to tag NYT articles. Two endpoints support the workflow: /search.json returns concepts matching a query string with optional concept-type filtering, and /name/{concept-type}/{specific-concept}.json returns the linked-data record for a single concept including article references, related concepts, and external resource links. The API is designed for entity linking, knowledge-graph enrichment, and disambiguating named entities mentioned in editorial content.

2 endpoints

Times Newswire API

The New York Times Times Newswire API is a real-time stream of NYT article URLs and metadata, updated as soon as articles are published on NYTimes.com or sourced from the Associated Press. Three GET endpoints return content from a chosen source (all, nyt, or iht), section, and time-period combination. Each item carries title, byline, abstract, publication date, web URL, geographic facets, organisational facets, and embedded multimedia, supporting near-real-time newsroom monitoring and downstream content distribution.

3 endpoints

TimesTags API

The New York Times TimesTags API is an autocomplete service over the NYT controlled vocabulary used to tag NYT articles. A single /timestags endpoint accepts a partial query string and returns ranked tag suggestions across persons, organizations, locations, descriptors, titles of works, and other entity types. Each suggestion includes the canonical tag string with a leading classifier (e.g. 'Per:', 'Org:', 'Geo:'), letting an autocomplete UI label suggestions by entity type. The API is the recommended front door for type-ahead lookups before deeper linked-data calls into the Semantic and Geographic APIs.

1 endpoints

Top Stories

The New York Times Top Stories API returns the editor-curated lineup of articles from any NYT section front. A single GET endpoint accepts a section name (such as home, world, business, technology, opinion, or arts) and returns the ranked article list with title, byline, abstract, kicker, web URL, geographic and organisational facets, and embedded multimedia at multiple sizes. The API mirrors the NYTimes.com section fronts and is ideal for surfacing curated section-level coverage rather than chronological wire feeds.

1 endpoints

Connect Your Agent

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.