Geographic API

Name: Geographic API API
Brand: Geographic API
Availability: InStock

✓ Official Vendor SpecData EnrichmentAddress ValidationapiKey1 EndpointsREST

For Agents

Resolve place names against the NYT geographic controlled vocabulary and return linked location data with coordinates and article references.

Quickstart

Get started with Geographic API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"resolve place name to NYT geographic concept"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Geographic API API.

Resolve a place name to its NYT geographic concept identifier

Retrieve linked-data attributes for a NYT location concept including coordinates

Filter geographic concepts by NYT facet vocabulary fields

Surface the NYT articles tagged with a specific location

GET STARTED

Start building with Geographic API API

Explore with Jentic

View OpenAPI Document

Use for: Resolve 'Brooklyn' to its NYT geographic concept, Find the latitude and longitude for a NYT-tagged location, Get all NYT articles tagged with a specific city, Search for geographic concepts matching a place name

Not supported: Does not provide street-level geocoding, routing, or reverse geocoding for arbitrary addresses — use for resolving place names against the NYT controlled vocabulary only.

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.

Use Cases

Patterns agents use Geographic API API for, with concrete tasks.

★ Place Disambiguation in News Pipelines

Disambiguate place names extracted from text by resolving them against the NYT geographic controlled vocabulary. The /query.json endpoint accepts a place name and returns candidate concepts with country, region, and coordinate context, letting an agent pick the right entity before storing it in a downstream system. Useful for newsroom enrichment, knowledge graphs, and editorial automation.

Call /query.json with query='Cambridge' and return the candidate locations with country code so the agent can select the UK city versus the Massachusetts city.

Article Geographic Linking

Build a map-based news browser that lists every NYT article tagged with a chosen location. The Geographic API resolves the place to its NYT concept and the response includes references to associated articles, which can be combined with the Article Search API for full content lookup.

Resolve query='Kyiv, Ukraine' via /query.json, extract the geo concept identifier, and return the article references attached to the resolved record.

Knowledge Graph Enrichment

Enrich an internal knowledge graph with NYT-controlled-vocabulary geographic identifiers so that internal location records can be cross-referenced against published NYT coverage. The single /query.json endpoint provides a stable resolver suitable for batch enrichment runs.

Iterate through a list of internal city records and call /query.json for each to attach the matching NYT geo concept identifier.

Agent-Driven Location Lookup via Jentic

An AI research agent uses Jentic to resolve a place mentioned in conversation against the NYT geographic vocabulary. Jentic's intent search returns the /query.json operation, the agent loads the schema and executes the lookup without manually reading the NYT semantic linked-data documentation.

Search Jentic for 'resolve place name to NYT concept', load the /query.json operation, and execute it with query='Mumbai, India'.

Key Endpoints

1 endpoints — 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.

METHOD

PATH

DESCRIPTION

GET

/query.json

Resolve a place name or concept query to NYT geographic records

GET

/query.json

Resolve a place name or concept query to NYT geographic records

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The NYT api-key is stored encrypted in the Jentic vault and injected into the api-key query parameter at execution time. A single key authenticates every NYT API in the workspace, so rotating one credential refreshes Geographic, Semantic, TimesTags, and the others together.

Intent-based discovery

Agents search Jentic with phrases like 'resolve place name to NYT concept' or 'look up NYT geographic vocabulary'. Jentic returns the /query.json operation with its parameter schema, so the agent calls it without reading the linked-data documentation.

Time to first call

Direct integration: a few hours to read the NYT linked-data semantics, wire the api-key, and parse the geo facet structure. Through Jentic: under 15 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

NYT Semantic API

Parent vocabulary API resolving people, organizations, and descriptors that the Geographic API extends with locations.

Use Semantic API for non-geographic concepts; switch to Geographic API for place-name disambiguation specifically.

Alternative

NYT TimesTags API

Autocomplete-style tag matcher across the full NYT vocabulary including geographies.

Choose TimesTags for fast type-ahead suggestions; use Geographic API when you need full linked-data enrichment for a single location.

Complementary

NYT Top Stories API

Returns top NYT articles by section that can be filtered by geographic tag.

Combine resolved geographic concepts with Top Stories to surface section-level articles for a chosen place.

FAQs

Specific to using Geographic API API through Jentic.

What authentication does the NYT Geographic API use?

The Geographic API uses an API key passed as the api-key query parameter on /query.json. Provision a key at developer.nytimes.com. Through Jentic, the key sits in the vault and is injected at execution time, keeping the secret out of agent context.

What does the Geographic API return for a place query?

Each result is a NYT controlled-vocabulary geographic concept with a stable identifier, place name, country and region facets, latitude and longitude where available, and references to associated NYT articles. It does not return third-party point-of-interest data such as Google Places or OpenStreetMap entries.

What are the rate limits for the NYT Geographic API?

NYT enforces 500 requests per day and 5 requests per minute per API key shared across all NYT developer APIs. Plan batch enrichment runs accordingly and cache concept identifiers since they are stable.

How do I resolve a place name through Jentic?

Search Jentic for 'resolve place name to NYT concept', load the /query.json operation, and execute it with the query parameter set to the place string. The response returns ranked candidate concepts with facets for disambiguation.

Is the NYT Geographic API free to use?

Yes. NYT offers the Geographic API at no cost on the developer portal for non-commercial use within published rate limits. Commercial or high-volume use requires direct contact with the NYT licensing team.

Can I use this API for full-text geocoding of arbitrary addresses?

No. The Geographic API resolves names against the NYT controlled vocabulary, not against a full address geocoder. For street-level geocoding use a dedicated mapping API such as Google Maps or HERE; use the NYT API only when linking text to NYT coverage.