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
Wikidata website screenshot

Wikidata

Wikidata is a free, collaborative, multilingual knowledge graph hosted by the Wikimedia Foundation. It provides structured linked data for Wikipedia and other Wikimedia projects, as well as a public platform for anyone to read and edit. Wikidata exposes several APIs including a Wikibase REST API for entity read/write operations, the MediaWiki Action API for batch entity retrieval and editing, a SPARQL endpoint for complex graph queries, Linked Data URIs for individual entity access in multiple RDF formats, a real-time Server-Sent Events stream for change monitoring, and full database dumps for bulk data processing.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Wikidata the way a machine reads it — 81 machine-readable artifacts across 1 API, 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 — Wikidata scores 59.6/100 (strong), with a separate agent-readiness read of 30/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
Wikidata Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Wikidata'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/wikidata/"
   title="Wikidata on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/wikidata.svg"
       alt="Wikidata 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 Wikidata

Each block below is one kind of artifact we hold for Wikidata. 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 9

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 Action API

The MediaWiki Action API provides batch entity retrieval, editing, and search for Wikidata via wbgetentities, wbsearchentities, wbeditentity, and other actions. Supports up to 5...

SPARQL Query Service

The Wikidata Query Service provides a SPARQL 1.1 endpoint at query.wikidata.org for running complex graph queries over the full Wikidata knowledge base. Supports federated queri...

Linked Data Interface

The Wikidata Linked Data Interface provides individual entity data via content negotiation at http://www.wikidata.org/entity/{QID}. Supports JSON, JSON-LD, RDF/XML, Turtle, and ...

Recent Changes Event Stream

The Wikimedia Event Stream provides real-time Server-Sent Events (SSE) for Wikidata changes, revision creations, and page events. Available at stream.wikimedia.org. Ideal for mo...

Wikidata Descriptions API

Description management

Wikidata Items API

Wikidata item (Q-entity) operations

Wikidata Labels API

Label management

Wikidata Properties API

Wikidata property (P-entity) operations

Wikidata Statements API

Statement (claim) operations

Scroll within the panel for all 9 ·

Postman Collections 5

A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.

Ready-to-run Postman collections for exercising this provider's APIs.

Open Collections 7

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

Scroll within the panel for all 7 ·

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.

Wikidata Rate Limits

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

Features 8

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 Support

All entities support labels, descriptions, and aliases in hundreds of languages via BCP 47 language codes.

Structured Statements

Every claim is modeled as a statement with property, value, rank, qualifiers, and references for full provenance.

Open License

All Wikidata content is released under CC0 1.0 Universal (Public Domain) — no attribution required.

SPARQL Graph Queries

Complex multi-hop queries over 100M+ entities via SPARQL 1.1 at query.wikidata.org with GeoSPARQL and time extensions.

Real-Time Event Streaming

Server-Sent Events at stream.wikimedia.org deliver real-time change notifications for Wikidata edits.

Multiple Serialization Formats

Entities available as JSON, JSON-LD, RDF/XML, Turtle, and N-Triples via content negotiation on Linked Data URIs.

Wikibase Federation

Wikidata is an instance of Wikibase; federated SPARQL queries can cross Wikibase instances including Wikimedia Commons.

Database Dumps

Full JSON and RDF/TTL database dumps refreshed weekly at dumps.wikimedia.org for local bulk processing.

Scroll within the panel for all 8 ·

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

Wikidata Context

10 classes · 27 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.

Wikidata API Rules

5 rules · 4 warnings

SPECTRAL

Wikidata API Rules

37 rules · 12 errors · 20 warnings

SPECTRAL

JSON Schema 9

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.

DataValue

2 properties

JSON SCHEMA

Wikidata Entity

10 properties

JSON SCHEMA

ItemCreate

6 properties

JSON SCHEMA

Item

7 properties

JSON SCHEMA

PatchRequest

4 properties

JSON SCHEMA

Property

5 properties

JSON SCHEMA

Sitelink

3 properties

JSON SCHEMA

StatementCreate

6 properties

JSON SCHEMA

Statement

6 properties

JSON SCHEMA

Scroll within the panel for all 9 ·

JSON Structure 9

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.

Wikidata Data Value Structure

2 properties

JSON STRUCTURE

Wikidata Entity Structure

10 properties

JSON STRUCTURE

Wikidata Item Create Structure

6 properties

JSON STRUCTURE

Wikidata Item Structure

7 properties

JSON STRUCTURE

Wikidata Patch Request Structure

4 properties

JSON STRUCTURE

Wikidata Property Structure

5 properties

JSON STRUCTURE

Wikidata Sitelink Structure

3 properties

JSON STRUCTURE

Wikidata Statement Create Structure

6 properties

JSON STRUCTURE

Wikidata Statement Structure

6 properties

JSON STRUCTURE

Scroll within the panel for all 9 ·

Examples 9

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.

Scroll within the panel for all 9 ·

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.

Wikidata Authentication

apiKey/oauth2 · 2 schemes

SECURITY

Wikidata Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wikidata Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Wikidata Scopes

2 scopes · authorizationCode

2 scopes

SCOPES

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.

Wikidata Agentic Access

11 operations · 5 acting

11 operations · 5 acting

AGENTIC

Use Cases 7

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.

Knowledge Graph Augmentation

Enrich private datasets with structured Wikidata facts — entities, dates, relationships — via item and SPARQL queries.

Fact-Checking and Verification

Retrieve canonical statements with references to verify biographical, geographic, or scientific claims in text.

Wikipedia Infobox Data

Power Wikipedia infoboxes and sister-project templates with live Wikidata entity data via the MediaWiki Action API.

NLP Entity Linking

Resolve named entities from natural language to Wikidata Q-IDs using wbsearchentities and SPARQL label lookups.

Semantic Search

Build ontology-aware search systems using Wikidata's P31 (instance of) and P279 (subclass of) property hierarchies.

Change Monitoring

Track real-time edits to Wikidata entities relevant to a domain using the SSE event stream.

Linked Open Data Publishing

Publish organizational data as Linked Open Data by aligning custom schemas to Wikidata properties and Q-IDs.

Scroll within the panel for all 7 ·

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

Wikidata powers structured data for all Wikipedia language editions via Lua modules and infobox templates.

Wikimedia Commons

Media files on Wikimedia Commons are described using Wikidata items via structured data on Commons.

OpenStreetMap

OSM features are linked to Wikidata via the wikidata=* tag, enabling geographic entity cross-referencing.

Scholia

Scholia is a Wikidata-based scholarly profile service that visualizes publications, authors, and institutions.

Reasonator

Reasonator renders human-readable pages for Wikidata items, integrating maps, timelines, and media.

Mix'n'match

Mix'n'match links Wikidata items to external databases (VIAF, ORCID, GND, etc.) for authority control.

OpenRefine

OpenRefine has a Wikidata reconciliation service and can batch-upload tabular data as Wikidata statements.

Scroll within the panel for all 7 ·

Resources

Every other property we hold for Wikidata — 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 2

Pagination, idempotency, versioning, errors, and events

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

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

Where this information came from

This is an independent, third-party profile of Wikidata, 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.