Wikimedia Enterprise is a service of the Wikimedia Foundation available via enterprise.wikimedia.com. The goal of the service is to build services for high-volume commercial reusers of Wikimedia content. The service was announced in March 2021 (blogpost, WIRED article) and launched in October 2021 (Press release, OpenFutures article).
Idojukọ naa wa lori awọn ẹgbẹ ti o fẹ lati tun akoonu Wikimedia pada ni awọn aaye miiran, pese awọn iṣẹ data ni iwọn nla, ki wọn yara ati okeerẹ diẹ sii, igbẹkẹle, ati aabo. Idawọlẹ Wikimedia ni ero lati mu ilọsiwaju olumulo ti awọn oluka Wikimedia kọja awọn oju opo wẹẹbu tiwa; mu arọwọto ati iwari akoonu; ati ilọsiwaju imọ ati irọrun ti ikasi ati ijẹrisi nipasẹ awọn ajo ti o tun lo data akanṣe Wikimedia julọ — nipasẹ awọn iṣẹ igbeowosile ara ẹni.
Idiwo ti o ga pupọ wa si titẹsi fun lilo data Wikimedia, ni ita awọn ọran lilo ti o wọpọ ti kika tabi ṣiṣatunṣe. Eyi jẹ nitori pe akoonu jẹ lile fun awọn ẹrọ lati pin ati oye, eyiti o ni ipa lori bii data iṣẹ akanṣe Wikimedia ti de opin ilolupo ti ara wa, ati iwọn ipa ti o le ni.
In the Movement Strategy recommendations to increase the sustainability of our movement and improve user experience there are the recommendations to, respectively: "Explore new opportunities for both revenue generation and free knowledge dissemination through partnerships and earned income—for example...Building enterprise-level APIs," and "Make the Wikimedia API suite more comprehensive, reliable, secure and fast, in partnership with large scale users.... and improve awareness of and ease of attribution and verifiability for content reusers."
It is well known that a few massive companies use our projects' data. Those companies recognize that without the Wikimedia projects, they would not be able to provide as rich or reliable an experience to their own users. There has long been a feeling among community members that these companies should do more to reinvest in the Wikimedia communities for the benefits they gain from the content and resources they use.
This led to the idea of developing a new approach that is more sustainable in the long term and provides a much clearer relationship between Wikimedia and enterprise users. Most financial benefit for Wikimedia would likely only come from a very small handful of heavy for-profit users, and would feed back into the Wikimedia movement.
As this idea developed, it became clear there is a responsibility to democratize our data for organizations that do not possess the resources of these largest users, to ensure we are leveling the playing field and helping to foster a healthy internet without reinforcing monopolies. The benefits of such a service shouldn't just be for startups or alternatives to the internet giants, but also for universities and university researchers; archives and archivists; along with the wider Wikimedia movement.
Overview
Idojukọ Idawọlẹ Wikimedia wa lori awọn iṣowo ti o tun lo akoonu wa, ni igbagbogbo ni iwọn nla-fun apẹẹrẹ, ṣepọ sinu awọn aworan imọ, wiwa, awọn oluranlọwọ ohun, awọn maapu, ijabọ iroyin, awọn irinṣẹ agbegbe, awọn ohun elo ẹnikẹta, ati awọn iwadii iwadii kikun-corpus. Imudara ọpọlọpọ awọn data data ti Wikimedia lati fi igbekalẹ lẹhin akoonu wa ti a ko ṣeto yoo gba gbogbo awọn olumulo akoonu wa laaye lati pade awọn ibeere kọọkan wọn lakoko ti o tun ṣeto wa lati kọ awọn irinṣẹ ati awọn iṣẹ tuntun ni ọjọ iwaju, ti o wa fun gbogbo eniyan. Awọn atunlo akoonu wa n wa awọn paati pataki mẹta:
Frequency: Regular current snapshots of Wikimedia projects
Emphasizing a self-funding set of specific use cases allows the Wikimedia API team to focus on volunteers, teams, and organizations looking to access (and, most importantly, interact with) our data sets. This includes the majority of community editing tools, which will be out of scope for this service. For more information on improvements to the existing Wikimedia APIs see the service page on the "API Gateway" initiative.
Awọn ibi-afẹde eto:
'Akoonu: Ṣe diẹ sii ti akoonu iṣipopada wa ni awọn ọna kika ẹrọ deede, wa larọwọto fun gbogbo awọn oniwadi ati awọn olumulo tun-olumulo.
Iru-orisun: Din iwulo fun aaye-kikan-giga-scraping nipasẹ igbohunsafẹfẹ-igbohunsafẹfẹ ati awọn atunlo iwọn-giga, eyiti o fojusi lọwọlọwọ awọn olupin iṣelọpọ wa.
Ikowojo': Pese ọna ti o han gedegbe ati diẹ sii fun awọn olumulo tun-olumulo lati tun ṣe idoko-owo awọn anfani ti a mu pada si iṣipopada, dipo ṣiṣe awọn ẹbun altruistic lẹẹkọọkan ti o yatọ ni iwọn.
Community
Wikimania 2023 presentation slides
Contact [the team if you would like to arrange a conversation about this service with your community, at a time and meeting software platform of your choice.
Wikimedia projects are, have always been, and will always remain libre. The principles of free cultural works mean that anyone can use Wikimedia without restriction, including commercially. As a movement, we embrace this. It is why we reject ‘non-commercial’ licenses, as they would limit the kinds of reuse possible. And it is why we consider commercial reuse an important means of distributing knowledge to audiences.
Equally, Wikimedia projects are, have always been, and will always remain gratis. The ability to freely access the knowledge available across all Wikimedia projects has always been core to the mission of the Foundation and the movement. We provide this access not only to individuals visiting our websites but also programmatically to machines so that our content can be repurposed in other environments. The full corpus of Wikimedia content always has been, and will continue to be, made available for reuse in various forms (including but not limited to database dumps, APIs, and scraping) at no cost.
As a result, our content is often repurposed by for-profit organizations that rely on it to support their business models, and which consequently earn revenue from it. Outside of voluntary corporate donations to the Wikimedia Foundation, the movement has never received benefits from any of this revenue through return investment. In acknowledgement of this, under the heading of Increase the sustainability of our movement the Movement Strategy process asked the Wikimedia Foundation to explore, among other things, “enterprise-level APIs...models for enterprise-scale for-profit reusers, taking care to avoid revenue dependencies or other undue external influence in product design and development.” Furthermore, under the heading Improve User Experience, a further recommendation stated, "Make the Wikimedia API suite more comprehensive, reliable, secure, and fast, in partnership with large scale users where that aligns with our mission and principles, to improve the user experience of both our direct and indirect users, increase the reach and discoverability of our content and the potential for data returns, and improve awareness of and ease of attribution and verifiability for content reusers."
The Enterprise project team is developing a new resource aimed at for-profit content reusers, who have product, service, and system requirements that go beyond what we freely provide. Use of this offering will not be required for for-profit content reuse; companies can continue to use the current tools available at no cost. All Enterprise API revenue will unequivocally be used to support the Wikimedia mission—for example, to fund Wikimedia programs or help grow the Wikimedia Endowment.
This project represents a new kind of activity at the Foundation. The project is at a very early stage that should be considered a learning period. We will have successes, we will make mistakes, and we will need to adapt our strategies. The team is committed to listening, engaging, and where possible, integrating the feedback we get on our work. This document is organic and is reflective of the team's current thinking; we are attempting to document as much work as possible in the open. Up until now, our work has been shaped by a series of initial interviews with community members, Wikimedia Foundation Board and staff, researchers, and reusers.
Given the nature of the service, primary decision making for it will rest with the Wikimedia Foundation. We are seeking community input, in particular from the technical community and those who have been involved in the strategy process, throughout the lifetime of the service. Technical feedback has been gathered from colleagues at the Wikimedia Foundation, industry and research partners, technical partners across the movement, and with the broader technical communities via Phabricator. Input into the funding development side of the service will follow a similar pattern. We will continue gathering input via research interviews and focus groups, as well feedback here on Meta as per our principles.
Access
The primary use case of the suite of APIs is paid-access for large commercial organisations, with associated Service Level Agreements and dedicated customer support. Nevertheless, and in accordance with the project's project's principle of access for all, there are also various ways to access the Wikimedia Enterprise APIs for free.
Anyone can freely access by:
Creating an account on the official website and continually use the products there with a free account. This includes 5,000 On-demand API requests that refresh monthly (including the Structured Contents endpoint) and twice-monthly Snapshot API files in NDJSON format.
For the vast majority of use cases, these three options are more than sufficient.
Exceptional access
If you have a Wikimedia mission-aligned use case and your requirements exceed what is offered at no cost, you may request free exceptional access to the higher rate of the APIs.
If you would like to request this, please contact <techpartnershipswikimedia.org> with a response to the six criteria described below.
Requests will be reviewed by Wikimedia Foundation staff in accordance with the following criteria, and granted at the Wikimedia Foundation's discretion. If the request includes substantive access to Wikidata content, the request will be reviewed in coordination with staff from Wikimedia Deutschland.
Exceptional access criteria
1. Who (individual or organisation) is requesting exceptional access?
Please list the contact person’s name, organisation (if applicable), email address, and Enterprise API account username.
2. What is the request for?
Please specify what specific exception is being requested, and for what purpose. Please link to any documentation, existing service or project, research proposal, etc. that shows the use-case.
3. Need. Can the intended use-case be fulfilled via any of the existing free access methods?
Please specify how the existing public services (e.g. public database dumps, APIs, or bots, etc.) are insufficient for your needs.
Notes
Exceptional free access to a paid account can only be granted when all standard options are exhausted – including the free account of the Enterprise services. Possible examples include:
Persistent need for access above the Enterprise API requests/second, or datasets/month, free thresholds
Creation of a new feature/dataset
Formal customer-service or Service Level Agreement (SLA) requirements
4. Obligation. Would the intended use case require custom development to support or maintain? What is the duration of the requested exception?
Please specify if the proposal can be fulfilled using the features of the existing APIs and datasets. If necessary features or datasets are not already available, please clarify with reference to the published documentation.
Notes
Providing exceptional access is effectively a form of in-kind support. The value includes any initial and ongoing development support, and infrastructure expense (in particular, data transfer costs). Contributions back to the Wikimedia movement (e.g., through content donations and data reports, tools, infrastructure, volunteer support and activities, and technical collaborations) could be understood as reciprocal in-kind contributions.
In accordance with the Wikimedia Enterprise operating principles regarding non-exclusivity, any newly developed software feature or dataset must be made available to all. This might raise the financial cost of operating the service considerably, or decrease the strategic value of the proposed use case.
Please explain how the intended use will help the Wikimedia movement reach at least one of these goals.
Notes
There is no perfect definition of “mission alignment”. Nevertheless, the Movement Strategy recommendations (2020) represent the culmination of wide-ranging consultation across the Wikimedia community and stakeholders about our future. Its recommendations are broad in scope, stable, and independent of any one stakeholder’s needs.
Special consideration would be given to organizations serving marginalized communities, underrepresented languages, or Wikimedia sister projects. The proposed use-case should not deliberately create or reinforce closed knowledge silos, proprietary forks of the content, or circumvent community norms or policies.
6. Values alignment. Do the requester’s professional practices or business model align with Wikimedia’s values? Please explain how the request (individual or organization) is in support of these values.
Notes
A human rights assessment is undertaken by the WMF for certain users of paid accounts for the Enterprise APIs (regardless of payment or exceptional access), in accordance with the Human Rights Policy and Commercial Sales and Contracts Policy.
However, in order to receive free access to a paid account, the user should also be able to demonstrate a commitment to open knowledge, transparency, and/or public-benefit mission (such as education, cultural heritage, intergovernmental agency).
If requesting from a commercial organisation, specify if the lack of exceptional access would significantly jeopardize a public-benefit mission – essential for research, accessibility, public information or safety, for example.
The business-model should at the very least not be in conflict with Wikimedia’s values – for example by being built upon harmful misinformation, disinformation, human rights violations, extractive data use, unethical generative AI, or undisclosed paid-editing practices on Wikimedia sites.
If you have any questions, please leave a message on the Talkpage or email <techpartnershipswikimedia.org>
Over time, the "API products" offered will grow and improve. This information is accurate as of September 2024.
Overview
All of our APIs return the same structured JSON (or ND-JSON) response format making it easy to augment one API with another. Three APIs; same data with different retrieval methods:
Retrieve bulk data with the Snapshot API
Retrieve single articles with the On-demand API
Receive changes instantly with Realtime API streaming
API responses payloads include article data such as summary, image, Wikidata QID, license, and metadata specific to the last revision such as editor, size of change, and credibility score with revert probability. All data fields and schema are explained in detail on the project's Data Dictionary website page.
Snapshot API
For high-volume reusers that currently rely on the Wikimedia Dumps to access our information, we have created a solution to ingest Wikimedia content in near real-time without excessive API calls (On-demand API) or maintaining hooks into our infrastructure (Realtime).
The Enterprise Snapshot API allows users to retrieve entire Wikimedia projects as a database dump file.
Download a compressed file containing everything in any supported project, in any language
Article body in HTML as well as Wikitext
Up to a daily snapshots cadence
24-hour compressed dumps (with both wikitext and html) of supported "text-based" Wikimedia projects
A wide range of commercial and consolidated schemas under SLAs
SLA and Support
On-demand API
Reusers that use an infrastructure reliant on the EventStream platform depend on services like RESTBase to pull HTML from page titles and current revisions to update their products. High-volume reusers have requested a reliable means to gather this data, as well as structures other than HTML when incorporating our content into their KGs and products.
The Wikimedia Enterprise On-demand API allows users to retrieve single articles from any supported Wikimedia project at anytime.
Make standard HTTP requests to retrieve documents by name from all supported projects and languages with filters available to limit response
Request the latest page data anytime to augment your Realtime or Snapshot API data
A wide range of commercial and consolidated schemas under SLAs
Realtime API
High-volume reusers currently rely heavily on the changes that are pushed from our community to update their products in real-time, using EventStream APIs to access such changes. High-volume reusers are interested in a service that will allow them to filter the changes they receive to limit their processing, guarantee stable HTTP connections to ensure no data loss, and supply a more useful schema to limit the number of API calls they need to make per event.
The Enterprise Realtime API allows users to stream updates in real-time from any supported Wikimedia project.
Streaming: Receive streaming (firehose) updates of every change as they occur in real-time
Batch: Download compressed snapshot files of incremental updates every hour
Instant updates for new content, any edits, deletions, and breaking news events including community-curated visibility changes
Filtering of events by Project or Revision Namespace
A wide range of commercial and consolidated schemas under SLAs with guaranteed connections
Contracted accounts receive 99% SLA and support response-time guarantees. All accounts have access to our introductory onboarding resources and help center faqs.
Team
The Wikimedia Enterprise project is helmed by the Commercial Partnerships division, which sits under the Advancement Department in the Wikimedia Foundation. The following staff are part of Commercial Partnerships:
Many people from different teams also contribute significantly, including from the WMF Legal, Engineering, Partnerships, Design, Communications teams etc. Additional contract work provided by: PartnerHero provide customer support services; Vuurr are assisting our sales process; and Super Natural Design are the designers of the project website.
Engineering support was provided in the first years by Speed & Function.
Since December 2025, the division working on the Wikimedia Enterprise Initiative changed its name from 'Wikimedia Enterprise' to 'Commercial Partnerships', to reflect the inclusion of the Technical Partnerships team.
Governance
The board of the LLC overseeing the project are Ex officio from Wikimedia Foundation leadership, representing their Wikimedia Foundation staff roles. This includes the Chief Advancement Officer Lisa Seitz-Gruwell; General Counsel Stephen LaPorte; Chief Product and Technology Officer Selena Deckelman; and Lane Becker who serves as the LLC's president. The LLC is subject to the governance of the Wikimedia Foundation Board of Trustees as described on the Wikimedia Foundation Commercial Sales and Contracts Policy.
All reports and official documents of the LLC are published on a dedicated Wikimedia Enterprise page on the Wikimedia Foundation Governance website. For convenience, annual reports are also linked here:
Initial Wikimedia Foundation Diff blogpost note: media stories listed below are written and published independently and were neither pre-reviewed nor approved by the WMF
25th Birthday customer announcement - January 2026
Wikimedia Foundation Press release & Wikimedia Enterprise blogpost note: media stories listed below are written and published independently and were neither pre-reviewed nor approved by the WMF. Some publications described this as a "licensing" deal - which is a misrepresentation.
Wikitech: Awọn iṣẹ data portal – Atokọ awọn iṣẹ ti o dojukọ agbegbe ti o gba laaye fun iraye si taara si awọn ibi ipamọ data ati idalẹnu, bakanna bi awọn oju opo wẹẹbu fun ibeere ati iraye si eto si awọn ile itaja data.
Ibudo Idawọlẹ – oju-iwe kan fun awọn ti o nifẹ si lilo sọfitiwia MediaWiki ni awọn ipo ajọ.
Ẹgbẹ MediaWiki – ẹgbẹ alafaramo ti o ni ominira ti o ṣe agbero fun awọn iwulo awọn olumulo MediaWiki ni ita Wikimedia Foundation, pẹlu awọn ile-iṣẹ ti o ni ere.
wikimedia.org> with a response to the six criteria described below.
Christopher Petrillo
Stephanie Delbecque
Luvo Dlulisa
Ruairi O'Donnell
Ehi Enabulele
,_Innenhafen_--_2017_--_1699.jpg)
