MDN Web Docs APIunofficial

Search English web platform documentation, read article sections, and inspect browser compatibility data without an account.

mozilla.org

all live 3 operations, checked by the installs that call them.

Seeded by the maintainers.

Try it

Set up API Anything for your agents:

npx -y api-anything setup

Then ask your agent, which finds this site by itself, or call it from a shell:

api-anything pull mdn
api-anything call mdn getCompat feature=api.fetch

Operations

Operation	Method	Login	Writes	Status
`getCompat(feature) -> support, status, mdn_url` Read browser support statements and status for a browser compatibility data feature.	GET	no	no	Live0 confirmations · success unknown; last worked unknown
`getDoc(slug) -> title, sections, lastModified` Read an English MDN page's title, last modified date, and rendered section text.	GET	no	no	Live0 confirmations · success unknown; last worked unknown
`searchDocs(q) -> title, slug, url, summary, score` Search English MDN documentation, returning the first page of results.	GET	no	no	Live0 confirmations · success unknown; last worked unknown

Notes

These reads need no account and cover English MDN pages. Documentation content is generally licensed under CC BY-SA; see the page's license and attribution requirements before reuse.

Search returns the first 10 results. Use a result's url path after /en-US/docs/ as the document slug, preserving case; the search slug itself is lowercased. Redirecting aliases can work too.
Document sections are plain rendered text with their headings included where present, not structured heading/text pairs. The first section is usually the introduction. Code formatting and whitespace are not preserved; some markup artifacts can remain. The compatibility section may be empty because its table loads separately. The last-modified date may be absent.
Results are capped at 20,000 JSON characters. Check truncated: a long document can lose later sections or shorten a section.
Compatibility keys are case-sensitive BCD identifiers, not documentation slugs. Support is keyed by browser or runtime, with arrays of support statements; inspect all statements, including flags, notes and version removals. This returns the requested feature's own support, not its nested subfeatures.

About these operations

Each operation is a request learned from MDN Web Docs's own web pages: API Anything replays it over plain HTTP and falls back to a browser when it must. Read them as JSON.

← All shared sites