Open static data

Use the records.
Do not scrape the layout.

Every public dataset is generated from the same source files as the dictionary pages. Endpoints are static, cacheable, versioned in their payloads where appropriate, and require no API key.

2.0.0Current schema release

3Regional packs

JSONPrimary interchange format

0Authentication requirements

Endpoint directory

Stable, inspectable outputs.

Use canonical URLs from the records when linking back to a meaning. Cache JSON according to the response headers rather than assuming it never changes.

01/data/index.json

Complete normalized entry records

Entry index ↗02/data/search-index.json

Compact search payload

Search ↗03/data/relations.json

Relationship nodes and explained edges

Graph ↗04/data/languages.json

Regional language and definition-language metadata

Language ↗05/data/routes.json

Canonical route, output path, type, language, and revision data

SEO ↗06/data/release-manifest.json

Build version, source hashes, route counts, and generated-file checksums

Release ↗07/data/regions/boston.json

One complete regional pack

Region ↗08/data/entries/boston/wicked.json

One granular entry record

Entry ↗

01 · Attribution

Link to the canonical entry.

Definitions carry regional scope and editorial status. Preserve that context when reusing a record.

02 · Versioning

Read the manifest before a bulk refresh.

The release manifest exposes build version and checksums so consumers can identify meaningful dataset changes.

03 · Privacy

Static endpoints set no user account requirement.

LocalMean does not need a personalized API profile to serve public dictionary data.

Example

Fetch one entry

const response = await fetch('https://localmean.com/data/entries/boston/wicked.json');
const entry = await response.json();
console.log(entry.term, entry.definition, entry.url);