Wikipedia & Wikidata API - Entity Facts, Summary & Pageviews avatar

Wikipedia & Wikidata API - Entity Facts, Summary & Pageviews

Pricing

from $2.55 / 1,000 entity resolveds

Go to Apify Store
Wikipedia & Wikidata API - Entity Facts, Summary & Pageviews

Wikipedia & Wikidata API - Entity Facts, Summary & Pageviews

Wikipedia & Wikidata API: give any company, person, place or thing and get one structured record: summary, Wikidata ID, key facts (country, founded, HQ, CEO, website, industry...), image and 30-day pageviews. Use it for LLM grounding and entity enrichment. Keyless, bulk.

Pricing

from $2.55 / 1,000 entity resolveds

Rating

0.0

(0)

Developer

Centor Prat

Centor Prat

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

🧩 Wikipedia & Wikidata API: Entity Facts, Summary & Pageviews

One call, Wikipedia + Wikidata, one brief. Give an entity name (company, person, place, thing) and get a single structured brief — summary, resolved facts (type, country, inception, website, HQ, industry, CEO, founder, population, revenue…), coordinates, and a 30-day popularity signal — instead of scraping Wikipedia and crawling Wikidata yourself.

Headless · keyless · structured JSON out · built for AI agents (grounding & enrichment).

⚡ Why it's different

Other actors dump raw Wikipedia text. This one resolves and fuses: it maps the page to its Wikidata entity, pulls the structured claims, resolves their labels, and adds popularity — so you get ceo: Sam Altman, country: United States, inception: 2015-12-11, not a wall of prose.

📋 What you get (per entity)

FieldMeaning
title, wikidataIdResolved canonical name + Wikidata QID
description, extractShort description + lead summary
factsStructured: instanceOf, country, inception, officialWebsite, headquarters, industry, ceo, founder, capital, population, employees, revenueUsd, motto
coordinateslat/lon (for places/HQs)
url, thumbnailWikipedia page + image
monthlyPageviewsViews in the last 30 days (popularity)
isDisambiguation, resolvedFlags for ambiguous/unfound names

📥 Input

FieldTypeMeaning
entitystringA single name, e.g. OpenAI
entitiesarrayMany names: ["OpenAI","Spain","Bitcoin"] (billed per entity)
languagestringWikipedia language edition (default en)
webhookUrlstringPOST the briefs here (Zapier/Make/n8n/custom)

Example input

{ "entities": ["OpenAI", "Spain", "Bitcoin"], "language": "en" }

📤 Output (one row per entity)

{
"query": "OpenAI", "resolved": true, "title": "OpenAI", "wikidataId": "Q21708200",
"description": "American artificial intelligence company",
"extract": "OpenAI is an American artificial intelligence ...",
"url": "https://en.wikipedia.org/wiki/OpenAI", "thumbnail": "https://.../OpenAI_Logo.svg.png",
"coordinates": { "lat": 37.76, "lon": -122.41 },
"facts": {
"instanceOf": { "qid": "Q6881511", "label": "enterprise" },
"country": { "qid": "Q30", "label": "United States" },
"inception": { "value": "2015-12-11" },
"officialWebsite": { "value": "https://openai.com/" },
"ceo": { "qid": "Q7407093", "label": "Sam Altman" },
"industry": { "qid": "Q11660", "label": "artificial intelligence" },
"employees": { "value": 4500 }
},
"hasFacts": true, "monthlyPageviews": 354585,
"sources": ["wikipedia.org", "wikidata.org", "wikimedia.org (pageviews)"],
"capturedAt": "2026-..."
}

💰 Pricing (pay-per-event menu)

  • entity-resolved — base, per entity returned.
  • facts-enriched — premium, per entity that yields structured Wikidata facts (the high-value outcome).

💡 Use cases

  • Agent grounding / disambiguation: resolve "Apple" → the company, with QID + facts, in one call.
  • Enrichment: turn a list of company/person names into structured records.
  • RAG / knowledge: fetch a vetted summary + facts + source URL to ground an answer.
  • Research dashboards: popularity (pageviews) + key facts across many entities.

🤖 For AI agents (MCP)

Keyless, one call → a resolved, fused, structured brief with the Wikidata QID for further hops. Example MCP server config:

{
"mcpServers": {
"entity-brief": {
"url": "https://mcp.apify.com/?tools=actors,docs,centorprat/wikipedia-wikidata-api"
}
}
}

Claude Code: claude mcp add --transport http apify "https://mcp.apify.com/?tools=actors,docs,centorprat/wikipedia-wikidata-api" --header "Authorization: Bearer <YOUR_APIFY_TOKEN>"

No extra setup: this Actor is callable from Claude, Cursor, ChatGPT or any MCP client through the Apify MCP server, and agents can find it on their own with the server's search-actors tool.

🚀 Ready-made tasks (one click)

Pre-configured runs for the most common jobs. Open one, change the input, run:

❓ FAQ

  • Do I need an API key? No — Wikipedia and Wikidata are keyless with generous limits.
  • What counts as an entity? Anything with a Wikipedia page: companies, people, places, products, concepts.
  • Ambiguous names? If the page is a disambiguation, isDisambiguation is true — refine the name.
  • Not found? resolved is false and the row carries just your query (so nothing is lost).
  • Which facts? A curated set of high-value Wikidata properties; item values are label-resolved.
  • Other languages? Yes — set language (e.g. es, de); facts/labels resolve in that language.
  • How fresh is popularity? monthlyPageviews sums the last ~30 days of Wikipedia views.
  • Is data stored? No — fetched, composed, returned.
  • Commercial use? Wikipedia & Wikidata are free content (CC BY-SA / CC0); attribute as appropriate.

📜 Data & attribution

Summaries from Wikipedia (CC BY-SA), structured facts from Wikidata (CC0), popularity from the Wikimedia pageviews API. Public data, composed and returned; nothing stored.

Part of one suite of keyless, agent-ready composers by the same developer: