Wiktionary
Wiktionary is the free, collaborative multilingual dictionary project of the Wikimedia Foundation, the dictionary sibling of Wikipedia. Programmatic access is exposed through the MediaWiki Action API at en.wiktionary.org/w/api.php, the older Wikimedia REST API at en.wiktionary.org/api/rest_v1/ (which provides Wiktionary-specific endpoints like /page/definition/{term}), and the newer MediaWiki Core REST API at en.wiktionary.org/w/rest.php. All Wiktionary content is licensed CC BY-SA 4.0 (and GFDL) and hosted by the Wikimedia Foundation.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Wiktionary the way a machine reads it — 143 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Wiktionary scores 66.9/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Wiktionary
Each block below is one kind of artifact we hold for Wiktionary. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Wiktionary Definition API
Wiktionary-specific structured multilingual definition endpoint
Wiktionary ExpandTemplates API
action=expandtemplates — Expand wikitext templates server-side
Wiktionary File API
File and media metadata
Wiktionary History API
Page history and revision details
Wiktionary OpenSearch API
action=opensearch — OpenSearch suggestions protocol
Wiktionary Page API
Page content, source, and HTML
Wiktionary Page Content API
Page HTML, summary, title metadata, and mobile-optimised HTML
Wiktionary Parse API
action=parse — Render wikitext to HTML and parse section trees
Wiktionary Query API
action=query — Fetch wikitext, extracts, revisions, and search results
Wiktionary Search API
Title-prefix and full-text search
Wiktionary Transform API
Parsoid wikitext ↔ HTML transforms and lint
Scroll within the panel for all 11 ·
Features 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Multilingual Definitions
/page/definition/{term} returns dictionary entries broken down by source language, part of speech, definitions, and usage examples in structured JSON.
Wikitext Access
action=query&prop=wikitext returns raw wikitext for any page, enabling clients to build their own parsers and extractors.
Rendered HTML
/page/html/{title} and action=parse return Parsoid-generated HTML suitable for direct rendering in client apps.
OpenSearch Suggestions
action=opensearch implements the OpenSearch suggestions protocol so Wiktionary can power autocomplete in any search UI.
Full-Text Search
action=query&list=search and /v1/search/page expose the same ElasticSearch-backed full-text search Wiktionary uses internally.
Page Revisions and History
Both APIs expose full revision history, supporting time-travel reads and change-detection workflows.
Wikitext ↔ HTML Transforms
Parsoid /transform/* endpoints convert between wikitext and HTML round-trip-safely, useful for visual editors and bots.
OAuth 2.0 and BotPasswords
Authenticated calls support OAuth 2.0 (via api.wikimedia.org), legacy OAuth 1.0a, and BotPassword scoped credentials.
CC BY-SA 4.0 License
All Wiktionary content can be reused for any purpose with attribution and share-alike, including in commercial AI training corpora.
Scroll within the panel for all 9 ·
Semantic Vocabularies 3
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Wiktionary API Rules
SPECTRALWiktionary API Rules
SPECTRALJSON Schema 32
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
FileMetadata
JSON SCHEMAHistoryCountResponse
JSON SCHEMAHistoryResponse
JSON SCHEMALatestRevision
JSON SCHEMALicenseInfo
JSON SCHEMAPageSourceResponse
JSON SCHEMAPageWithHtmlResponse
JSON SCHEMARevisionDetail
JSON SCHEMASearchPage
JSON SCHEMASearchResponse
JSON SCHEMAActionApiResponse
JSON SCHEMAExpandTemplatesResponse
JSON SCHEMAExtractPage
JSON SCHEMAOpenSearchResponse
JSON SCHEMAParseResponse
JSON SCHEMAParseSection
JSON SCHEMAQueryExtractsResponse
JSON SCHEMAQueryRevisionsResponse
JSON SCHEMAQuerySearchResponse
JSON SCHEMARevisionPage
JSON SCHEMARevision
JSON SCHEMASearchHit
JSON SCHEMAContentUrls
JSON SCHEMADefinitionEntry
JSON SCHEMADefinitionResponse
JSON SCHEMAHtmlTransformRequest
JSON SCHEMALanguageEntry
JSON SCHEMALintError
JSON SCHEMAPageSummary
JSON SCHEMARevisionItem
JSON SCHEMARevisionMetadata
JSON SCHEMAWikitextTransformRequest
JSON SCHEMAScroll within the panel for all 32 ·
JSON Structure 32
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Core Rest Api File Metadata Structure
JSON STRUCTURECore Rest Api History Count Response Structure
JSON STRUCTURECore Rest Api History Response Structure
JSON STRUCTURECore Rest Api Latest Revision Structure
JSON STRUCTURECore Rest Api License Info Structure
JSON STRUCTURECore Rest Api Page Source Response Structure
JSON STRUCTURECore Rest Api Page With Html Response Structure
JSON STRUCTURECore Rest Api Revision Detail Structure
JSON STRUCTURECore Rest Api Search Page Structure
JSON STRUCTURECore Rest Api Search Response Structure
JSON STRUCTUREMediawiki Action Api Action Api Response Structure
JSON STRUCTUREMediawiki Action Api Expand Templates Response Structure
JSON STRUCTUREMediawiki Action Api Extract Page Structure
JSON STRUCTUREMediawiki Action Api Open Search Response Structure
JSON STRUCTUREMediawiki Action Api Parse Response Structure
JSON STRUCTUREMediawiki Action Api Parse Section Structure
JSON STRUCTUREMediawiki Action Api Query Extracts Response Structure
JSON STRUCTUREMediawiki Action Api Query Revisions Response Structure
JSON STRUCTUREMediawiki Action Api Query Search Response Structure
JSON STRUCTUREMediawiki Action Api Revision Page Structure
JSON STRUCTUREMediawiki Action Api Revision Structure
JSON STRUCTUREMediawiki Action Api Search Hit Structure
JSON STRUCTURERest Api Content Urls Structure
JSON STRUCTURERest Api Definition Entry Structure
JSON STRUCTURERest Api Definition Response Structure
JSON STRUCTURERest Api Html Transform Request Structure
JSON STRUCTURERest Api Language Entry Structure
JSON STRUCTURERest Api Lint Error Structure
JSON STRUCTURERest Api Page Summary Structure
JSON STRUCTURERest Api Revision Item Structure
JSON STRUCTURERest Api Revision Metadata Structure
JSON STRUCTURERest Api Wikitext Transform Request Structure
JSON STRUCTUREScroll within the panel for all 32 ·
Examples 31
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Rest Api Lint Error Example
EXAMPLEScroll within the panel for all 31 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Dictionary Apps
Embed definitions, etymologies, pronunciations, and translations directly into mobile or desktop dictionary apps.
Language-Learning Tools
Power vocabulary lookups, flashcards, and reading-assistance browser extensions for learners of any language.
NLP and Linguistics Datasets
Use bulk wikitext dumps and the definition API to build morphology, inflection, and word-sense datasets for NLP research.
Translation Memory
Mine cross-language Wiktionary translation tables to seed bilingual dictionaries and translation memories.
Spell-Checkers and Tokenizers
Use the OpenSearch and search endpoints to validate word existence and segment text in tokenizers.
AI Grounding and RAG
Retrieve authoritative definitions to ground LLM responses about word meaning, etymology, and usage.
Crossword and Game Generation
Generate clues, anagrams, and puzzle answers from Wiktionary's definitions and word lists.
Linguistic Research
Query etymologies, declensions, pronunciations, and historical usage across hundreds of languages.
Scroll within the panel for all 8 ·
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Wikipedia
Shares infrastructure, accounts, and most APIs with Wikipedia; both run on MediaWiki under the Wikimedia Foundation.
Wikidata
Wiktionary lexemes are increasingly linked to structured Wikidata lexeme entities (Lexeme namespace, Q-IDs, L-IDs).
Wikimedia Commons
Pronunciation audio files and images embedded in Wiktionary pages live on Commons and are reachable via the same APIs.
Pywikibot
The reference bot framework for automated edits, dumps, and maintenance scripts against Wiktionary.
Wikimedia Enterprise
Commercial high-volume snapshots of Wikimedia content (Wikipedia first, with broader project coverage expanding); useful when REST rate limits are insufficient.
Toolforge
Wikimedia-hosted PaaS for community tools that consume the Wiktionary APIs at scale without bringing your own infrastructure.
Hugging Face Datasets
Pre-processed Wiktionary dumps are available on Hugging Face for immediate use in ML training pipelines.
Scroll within the panel for all 7 ·
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Free Public APIs
The MediaWiki Action API, Wikimedia REST API, and MediaWiki Core REST API are all free to use without registration, subject to the 200 req/s shared limit and User-Agent requirem...
Bulk Dumps
dumps.wikimedia.org provides full XML and SQL exports of every Wikimedia project, refreshed at least monthly; the preferred channel for whole-corpus processing.
Wikimedia Enterprise
Paid SLA-backed snapshots and streaming APIs for commercial reusers who need throughput, freshness, or attribution guarantees beyond what the free APIs provide.
Resources
Every other property we hold for Wiktionary — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 18
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 18 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/wiktionary · machine-readable index on apis.io