How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Wikipedia / MediaWiki website screenshot

Wikipedia / MediaWiki

Wikipedia is the free, multilingual online encyclopedia operated by the non-profit Wikimedia Foundation. The platform exposes its content and structured data through several public APIs: the original MediaWiki Action API (action=query|edit|parse|upload), the MediaWiki Core REST API (page CRUD, search, transforms), the Wikimedia REST API (page summaries, mobile HTML, math, citation, reading lists, recommendations), the Wikidata Query Service SPARQL endpoint (structured knowledge graph queries), and the Wikimedia Enterprise APIs (commercial Snapshot, On-demand, Realtime). All free APIs are governed by the Wikimedia API usage guidelines: contactable User-Agent, serial requests, maxlag for bots.

agent ready

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.

Kin Score

API Evangelist profiles Wikipedia / MediaWiki the way a machine reads it — 309 machine-readable artifacts across 2 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 — Wikipedia / MediaWiki scores 49.6/100 (developing), with a separate agent-readiness read of 34/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Wikipedia / MediaWiki Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Wikipedia / MediaWiki's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wikipedia/"
   title="Wikipedia / MediaWiki on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/wikipedia.svg"
       alt="Wikipedia / MediaWiki Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Wikipedia / MediaWiki

Each block below is one kind of artifact we hold for Wikipedia / MediaWiki. 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 19

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.

Wikipedia / MediaWiki Citation API

generation of citation data

Wikipedia / MediaWiki Mobile API

The Mobile API from Wikipedia / MediaWiki — 3 operation(s) for mobile.

Wikipedia / MediaWiki offline API

The offline API from Wikipedia / MediaWiki — 2 operation(s) for offline.

Wikipedia / MediaWiki Page content API

page content in different formats

Wikipedia / MediaWiki Reading lists API

Private lists of selected pages

Wikipedia / MediaWiki Recommendation API

contribution recommendations

Wikipedia / MediaWiki structured-contents API

(Beta) Structured Contents On-demand API

Wikipedia / MediaWiki structured-snapshots API

(BETA) Structured Contents Snapshot API

Wikipedia / MediaWiki Talk pages API

The Talk pages API from Wikipedia / MediaWiki — 2 operation(s) for talk pages.

Wikipedia / MediaWiki Transforms API

Wikitext <-> HTML transformation

Wikipedia / MediaWiki wikidata API

The wikidata API from Wikipedia / MediaWiki — 3 operation(s) for wikidata.

Scroll within the panel for all 19 ·

Open Collections 34

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Scroll within the panel for all 34 ·

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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Rate Limits 1

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.

Wikipedia Rate Limits

9 limits

RATE LIMITS

FinOps 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.

Semantic Vocabularies 6

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.

Wikipedia Context

7 classes · 0 properties

JSON-LD

Wikipedia Mediawiki Action Api Context

3 classes · 34 properties

JSON-LD

Wikipedia Mediawiki Core Rest Context

11 classes · 45 properties

JSON-LD

Wikipedia Rest V1 Context

20 classes · 56 properties

JSON-LD

Wikipedia Wikidata Sparql Context

1 classes · 5 properties

JSON-LD

Wikipedia Wikimedia Enterprise Context

44 classes · 87 properties

JSON-LD

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.

Wikipedia / MediaWiki API Rules

5 rules · 4 warnings

SPECTRAL

Wikipedia / MediaWiki API Rules

29 rules · 8 errors · 16 warnings

SPECTRAL

JSON Schema 81

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.

ActionApiError

4 properties

JSON SCHEMA

ActionApiWriteRequest

22 properties

JSON SCHEMA

ActionResult

8 properties

JSON SCHEMA

CompareResponse

3 properties

JSON SCHEMA

CreatePageRequest

5 properties

JSON SCHEMA

EditCounts

2 properties

JSON SCHEMA

File

5 properties

JSON SCHEMA

HistoryResponse

4 properties

JSON SCHEMA

LanguageLink

4 properties

JSON SCHEMA

Page

9 properties

JSON SCHEMA

Revision

10 properties

JSON SCHEMA

SearchResponse

1 properties

JSON SCHEMA

SearchResult

7 properties

JSON SCHEMA

UpdatePageRequest

5 properties

JSON SCHEMA

cx_dict

2 properties

JSON SCHEMA

cx_mt

1 properties

JSON SCHEMA

list_entry_read

5 properties

JSON SCHEMA

list_entry_write

2 properties

JSON SCHEMA

list_read

5 properties

JSON SCHEMA

list_write

2 properties

JSON SCHEMA

listing

2 properties

JSON SCHEMA

media_item

6 properties

JSON SCHEMA

media_list

3 properties

JSON SCHEMA

morelike_result

0 properties

JSON SCHEMA

originalimage

3 properties

JSON SCHEMA

problem

4 properties

JSON SCHEMA

recommendation_result

2 properties

JSON SCHEMA

result

3 properties

JSON SCHEMA

revisionIdentifier

2 properties

JSON SCHEMA

revisionInfo

12 properties

JSON SCHEMA

revision

2 properties

JSON SCHEMA

revisions

1 properties

JSON SCHEMA

summary

13 properties

JSON SCHEMA

thumbnail

3 properties

JSON SCHEMA

titles_set

3 properties

JSON SCHEMA

SparqlResults

3 properties

JSON SCHEMA

article_body

2 properties

JSON SCHEMA

article_namespace

1 properties

JSON SCHEMA

article

20 properties

JSON SCHEMA

batch

7 properties

JSON SCHEMA

category

2 properties

JSON SCHEMA

citation

3 properties

JSON SCHEMA

code

3 properties

JSON SCHEMA

editor

7 properties

JSON SCHEMA

entity

2 properties

JSON SCHEMA

event

3 properties

JSON SCHEMA

filter

2 properties

JSON SCHEMA

image

10 properties

JSON SCHEMA

language

4 properties

JSON SCHEMA

license

3 properties

JSON SCHEMA

link

3 properties

JSON SCHEMA

maintenance_tags

4 properties

JSON SCHEMA

namespace

3 properties

JSON SCHEMA

part

8 properties

JSON SCHEMA

project

5 properties

JSON SCHEMA

protection

3 properties

JSON SCHEMA

redirect

2 properties

JSON SCHEMA

reference

7 properties

JSON SCHEMA

referenceneed

1 properties

JSON SCHEMA

referencerisk

1 properties

JSON SCHEMA

revertrisk

2 properties

JSON SCHEMA

scores

3 properties

JSON SCHEMA

size

2 properties

JSON SCHEMA

snapshot

8 properties

JSON SCHEMA

structured-content

18 properties

JSON SCHEMA

table

4 properties

JSON SCHEMA

template

2 properties

JSON SCHEMA

thumbnail

3 properties

JSON SCHEMA

version

9 properties

JSON SCHEMA

visibility

3 properties

JSON SCHEMA

wikidata_article

13 properties

JSON SCHEMA

wikidata_entity_property

3 properties

JSON SCHEMA

wikidata_entity_qualifier

2 properties

JSON SCHEMA

wikidata_entity_reference_part

2 properties

JSON SCHEMA

wikidata_entity

7 properties

JSON SCHEMA

wikidata_entity_statement_reference

2 properties

JSON SCHEMA

wikidata_entity_value

4 properties

JSON SCHEMA

wikidata_labels

0 properties

JSON SCHEMA

wikidata_sitelinks

3 properties

JSON SCHEMA

wikidata_statement

6 properties

JSON SCHEMA

wikidata_statements

0 properties

JSON SCHEMA

Scroll within the panel for all 81 ·

JSON Structure 81

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.

Mediawiki Core Rest Edit Counts Structure

2 properties

JSON STRUCTURE

Mediawiki Core Rest File Structure

5 properties

JSON STRUCTURE

Mediawiki Core Rest Page Structure

9 properties

JSON STRUCTURE

Mediawiki Core Rest Revision Structure

10 properties

JSON STRUCTURE

Rest V1 Cx Dict Structure

2 properties

JSON STRUCTURE

Rest V1 Cx Mt Structure

1 properties

JSON STRUCTURE

Rest V1 List Entry Read Structure

5 properties

JSON STRUCTURE

Rest V1 List Entry Write Structure

2 properties

JSON STRUCTURE

Rest V1 List Read Structure

5 properties

JSON STRUCTURE

Rest V1 List Write Structure

2 properties

JSON STRUCTURE

Rest V1 Listing Structure

2 properties

JSON STRUCTURE

Rest V1 Media Item Structure

6 properties

JSON STRUCTURE

Rest V1 Media List Structure

3 properties

JSON STRUCTURE

Rest V1 Morelike Result Structure

0 properties

JSON STRUCTURE

Rest V1 Originalimage Structure

3 properties

JSON STRUCTURE

Rest V1 Problem Structure

4 properties

JSON STRUCTURE

Rest V1 Recommendation Result Structure

2 properties

JSON STRUCTURE

Rest V1 Result Structure

3 properties

JSON STRUCTURE

Rest V1 Revision Identifier Structure

2 properties

JSON STRUCTURE

Rest V1 Revision Info Structure

12 properties

JSON STRUCTURE

Rest V1 Revision Structure

2 properties

JSON STRUCTURE

Rest V1 Revisions Structure

1 properties

JSON STRUCTURE

Rest V1 Summary Structure

13 properties

JSON STRUCTURE

Rest V1 Thumbnail Structure

3 properties

JSON STRUCTURE

Rest V1 Titles Set Structure

3 properties

JSON STRUCTURE

Wikidata Sparql Sparql Results Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Article Structure

20 properties

JSON STRUCTURE

Wikimedia Enterprise Batch Structure

7 properties

JSON STRUCTURE

Wikimedia Enterprise Category Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Citation Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Code Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Editor Structure

7 properties

JSON STRUCTURE

Wikimedia Enterprise Entity Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Event Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Filter Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Image Structure

10 properties

JSON STRUCTURE

Wikimedia Enterprise Language Structure

4 properties

JSON STRUCTURE

Wikimedia Enterprise License Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Link Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Namespace Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Part Structure

8 properties

JSON STRUCTURE

Wikimedia Enterprise Project Structure

5 properties

JSON STRUCTURE

Wikimedia Enterprise Protection Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Redirect Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Reference Structure

7 properties

JSON STRUCTURE

Wikimedia Enterprise Revertrisk Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Scores Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Size Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Snapshot Structure

8 properties

JSON STRUCTURE

Wikimedia Enterprise Table Structure

4 properties

JSON STRUCTURE

Wikimedia Enterprise Template Structure

2 properties

JSON STRUCTURE

Wikimedia Enterprise Thumbnail Structure

3 properties

JSON STRUCTURE

Wikimedia Enterprise Version Structure

9 properties

JSON STRUCTURE

Wikimedia Enterprise Visibility Structure

3 properties

JSON STRUCTURE

Scroll within the panel for all 81 ·

Examples 79

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 V1 Cx Dict Example

2 fields

EXAMPLE

Rest V1 Cx Mt Example

1 fields

EXAMPLE

Rest V1 List Read Example

5 fields

EXAMPLE

Rest V1 Listing Example

2 fields

EXAMPLE

Rest V1 Problem Example

4 fields

EXAMPLE

Rest V1 Result Example

3 fields

EXAMPLE

Rest V1 Revision Example

2 fields

EXAMPLE

Rest V1 Revisions Example

1 fields

EXAMPLE

Rest V1 Summary Example

13 fields

EXAMPLE

Rest V1 Thumbnail Example

3 fields

EXAMPLE

Scroll within the panel for all 79 ·

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.

Wikipedia Authentication

apiKey/http · 2 schemes

SECURITY

Wikipedia Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wikipedia Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Wikipedia Agentic Access

125 operations · 49 acting · 1 human-in-the-loop

125 operations · 49 acting

AGENTIC

Resources

Every other property we hold for Wikipedia / MediaWiki — 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 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Operate 2

Status, limits, changes, and where to get help

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/wikipedia · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Wikipedia / MediaWiki, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.