Some web AI readers can fetch raw JSON or XML but do not display the body as readable page text.
This guide gives those readers a stable orientation surface while preserving the raw files as the canonical machine-readable sources.
OathAI publishes raw machine-readable files for automated readers, crawlers, and agents. Some webpage-style AI readers can retrieve those files but may not display raw JSON or XML as readable page text.
This page is a compatibility orientation surface. It explains the files, their roles, and the fields readers should look for. The raw files remain canonical.
For first-phase language layers, use the language sections and reading orders in llms-full.txt. Public language glossary pages exist where a language layer has released a reviewed core glossary; the global glossary.json records locale status for machine readers.
glossary.json is a compact machine index, not a human glossary page. Readers should expect fields such as:
version: file version.status: current role of the file as a public orientation index.canonical_pages: human glossary pages that are full glossary equivalents.terms: term records with identifiers, labels, definitions, and language fields.locale_status: per-language maturity and public-rendering status.do_not_confuse_with: boundaries that reduce semantic drift.This page does not certify crawler behavior, search indexing, AI interpretation, or downstream reuse. It does not replace glossary.json, sitemap.xml, llms.txt, or llms-full.txt.
Its job is simpler: give webpage-style readers a visible explanation of files that may otherwise be fetched as raw data but not displayed as readable body text.