Wikimedia
Wikimedia provides REST APIs for accessing Wikipedia, Wikidata, Commons, and other Wikimedia project content including page summaries, search, media files, page revision history, and usage metrics. The suite includes the MediaWiki Action API for bot and edit operations, the MediaWiki REST API for modern content access, and the Wikimedia Enterprise API for commercial-scale high-volume data reuse across 920+ datasets and 360+ languages.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Wikimedia the way a machine reads it — 103 machine-readable artifacts across 20 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 — Wikimedia scores 52.8/100 (developing), 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 Wikimedia
Each block below is one kind of artifact we hold for Wikimedia. 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 20
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.
MediaWiki REST API
The MediaWiki REST API provides a modern RESTful interface for reading and writing wiki content including pages, revisions, file metadata, search, and content transformation bet...
Wikimedia articles API
On-demand API
Wikimedia batches API
Realtime Batch API
Wikimedia Citation API
generation of citation data
Wikimedia codes API
Metadata
Wikimedia languages API
Metadata
Wikimedia Math API
formula rendering
Wikimedia Mobile API
The Mobile API from Wikimedia — 3 operation(s) for mobile.
Wikimedia namespaces API
Metadata
Wikimedia offline API
The offline API from Wikimedia — 2 operation(s) for offline.
Wikimedia Page content API
page content in different formats
Wikimedia projects API
Metadata
Wikimedia Reading lists API
Private lists of selected pages
Wikimedia Recommendation API
contribution recommendations
Wikimedia snapshots API
Snapshot API
Wikimedia structured-contents API
(Beta) Structured Contents On-demand API
Wikimedia structured-snapshots API
(BETA) Structured Contents Snapshot API
Wikimedia Talk pages API
The Talk pages API from Wikimedia — 2 operation(s) for talk pages.
Wikimedia Transforms API
convert content between HTML and Wikitext
Wikimedia wikidata API
The wikidata API from Wikimedia — 3 operation(s) for wikidata.
Scroll within the panel for all 20 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Wikimedia Enterprise
PLANSRate Limits 4
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mediawiki Action Api
RATE LIMITSMediawiki Rest Api
RATE LIMITSWikimedia Enterprise Api
RATE LIMITSWikimedia Rest Api
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Wikimedia Enterprise
FINOPSSemantic Vocabularies 1
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.
Wikimedia Context
JSON-LDSpectral Rules 1
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.
Wikimedia API Rules
SPECTRALJSON Schema 66
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.
article
JSON SCHEMAarticle_body
JSON SCHEMAarticle_namespace
JSON SCHEMAbatch
JSON SCHEMAcategory
JSON SCHEMAcitation
JSON SCHEMAcode
JSON SCHEMAcx_dict
JSON SCHEMAcx_mt
JSON SCHEMAeditor
JSON SCHEMAentity
JSON SCHEMAerror
JSON SCHEMAevent
JSON SCHEMAfilter
JSON SCHEMAimage
JSON SCHEMAlanguage
JSON SCHEMAlicense
JSON SCHEMAlink
JSON SCHEMAlist_entry
JSON SCHEMAlist_entry_write
JSON SCHEMAlist
JSON SCHEMAlist
JSON SCHEMAlisting
JSON SCHEMAmaintenance_tags
JSON SCHEMAmedia_item
JSON SCHEMAmedia_list
JSON SCHEMAmorelike_result
JSON SCHEMAnamespace
JSON SCHEMAoriginalimage
JSON SCHEMApart
JSON SCHEMAproblem
JSON SCHEMAproject
JSON SCHEMAprotection
JSON SCHEMArecommendation_result
JSON SCHEMAredirect
JSON SCHEMAreference
JSON SCHEMAreferenceneed
JSON SCHEMAreferencerisk
JSON SCHEMAresult
JSON SCHEMArevertrisk
JSON SCHEMArevision
JSON SCHEMArevisionIdentifier
JSON SCHEMArevisionInfo
JSON SCHEMArevisions
JSON SCHEMAscores
JSON SCHEMAsize
JSON SCHEMAsnapshot
JSON SCHEMAstructured-content
JSON SCHEMAsummary
JSON SCHEMAtable
JSON SCHEMAtemplate
JSON SCHEMAthumbnail
JSON SCHEMAtitles_set
JSON SCHEMAversion
JSON SCHEMAvisibility
JSON SCHEMAwikidata_article
JSON SCHEMAwikidata_entity
JSON SCHEMAwikidata_entity_property
JSON SCHEMAwikidata_entity_qualifier
JSON SCHEMAwikidata_entity_reference_part
JSON SCHEMAwikidata_entity_statement_reference
JSON SCHEMAwikidata_entity_value
JSON SCHEMAwikidata_labels
JSON SCHEMAwikidata_sitelinks
JSON SCHEMAwikidata_statement
JSON SCHEMAwikidata_statements
JSON SCHEMAScroll within the panel for all 66 ·
Examples 5
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.
Enterprise Article
EXAMPLEEnterprise Snapshot
EXAMPLEMedia List
EXAMPLEPage Revision
EXAMPLEPage Summary
EXAMPLESecurity 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.
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.
Resources
Every other property we hold for Wikimedia — 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wikimedia · machine-readable index on apis.io