Wikidata Entity Lookup

Look up any Wikidata entity by QID against the official, free Special:EntityData JSON export at www.wikidata.org — label, description, aliases, and a curated set of key claims (instance-of, inception date, official website, country, founder, headquarters, industry) resolved to human-readable labels, not raw property IDs. No API key, no scraping — this hits Wikidata's own public data export directly.

Features

• QID → structured entity record. Label, description, aliases, and a Wikidata URL for every entity that resolves.
• Claims resolved to labels, not raw IDs. Wikidata entities carry property-ID claims like P31 and P571 that mean nothing on their own. This actor resolves the common ones — instance-of, inception date, official website, country, founder, headquarters, industry — to plain-English labels via a single follow-up batch request, instead of dumping bare QIDs like Q6881511 in your data.
• Accepts QIDs or Wikidata URLs. Paste Q95 or https://www.wikidata.org/wiki/Q95 — both normalize the same way.
• Pay only for hits. QIDs that don't resolve cost nothing — see Pricing.
• Built for bulk. Feed in thousands of QIDs; concurrency, keyword filtering, and column selection are all configurable.

How to use Wikidata Entity Lookup — QID to Structured Facts API

1. In the Apify Console. Open the actor page and click Start — the qids field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~wikidata-entity-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"qids":["Q95"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "qids": [
    "Q95"
  ]
}

One Wikidata entity ID per line, e.g. Q95. Accepted formats: Q95, https://www.wikidata.org/wiki/Q95.

{
  "qids": ["Q95", "https://www.wikidata.org/wiki/Q95"],
  "testRun": false,
  "onlyFound": false,
  "maxConcurrency": 5
}

qids is a list of Wikidata entity IDs, one per line. Accepted formats are a bare QID (Q95) or a full Wikidata URL (https://www.wikidata.org/wiki/Q95) — both are normalized to the QID before lookup. You're only charged for QIDs that actually resolve; a miss costs nothing.

Other inputs:

• testRun — process only the first 5 QIDs, useful for a cheap sanity check before running the full list.
• onlyFound — drop rows with no result from the output. Misses are always free whether or not you show them.
• includeKeywords / excludeKeywords — optionally keep or drop rows based on whether the result text contains given words.
• maxResults — stop the run once this many results have been found.
• columns — pick which fields to include per row: label, qid, description, aliases, instanceOf, inceptionDate, officialWebsite, country, founder, headquarters, industry, wikidataUrl. All are included by default.
• maxConcurrency — parallel requests, default 5, max 20. This target has no browser fallback, so keeping it conservative avoids getting blocked.
• proxyConfiguration — Apify Proxy config; residential is recommended for anti-bot-sensitive targets.

Output

query	found	status	label	qid	description	aliases	instanceOf	inceptionDate	officialWebsite	country	founder	headquarters	industry	wikidataUrl	scrapedAt
Q95	true	OK	Google	Q95	American multinational technology company, a subsidiary of Alphabet Inc.	[]	business	1998-09-04	https://about.google/	United States	Sergey Brin	Mountain View	Internet industry	https://www.wikidata.org/wiki/Q95	2026-08-23T21:05:20.041Z

One row per QID, for example:

{
  "query": "Q95",
  "found": true,
  "status": "OK",
  "label": "Google",
  "qid": "Q95",
  "description": "American multinational technology company",
  "aliases": ["Google LLC", "Google Inc."],
  "instanceOf": "technology company",
  "inceptionDate": "1998-09-04",
  "officialWebsite": "https://www.google.com/",
  "country": "United States of America",
  "founder": "Larry Page",
  "headquarters": "Mountain View",
  "industry": "computer software",
  "wikidataUrl": "https://www.wikidata.org/wiki/Q95",
  "scrapedAt": "2026-08-21T00:00:00.000Z"
}

QIDs that don't resolve still get a row (unless onlyFound is on) with found: false and a status of NOT_FOUND (no such entity) or BAD_FORMAT (input wasn't a recognizable QID) plus a plain-English message — these rows are never charged.

Use cases

• Enrich a list of companies, people, or products you only have Wikidata QIDs for with readable names, founders, countries, and websites.
• Bulk-resolve entity references found in other datasets (e.g. Wikipedia infoboxes, knowledge-graph exports) into structured, labeled facts.
• Build a lightweight company or organization directory using inception date, headquarters, and industry pulled straight from Wikidata.
• Cross-check or backfill official websites and founders for a list of organizations without manually opening each Wikidata page.
• Feed a research or fact-checking pipeline with clean, labeled claims instead of raw Wikidata property IDs.

Pricing

$4 per 1,000 QIDs, plus a $0.005 start fee. Misses (found:false) are never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~wikidata-entity-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"qids":["Q95"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~wikidata-entity-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"qids":["Q95"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~wikidata-entity-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"qids":["{{QID}}"]}, mapping the row's QID into the qids array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Wikidata API — QID to Structured Entity Facts" — the agent will find and run this actor.

FAQ

What counts as a "found" entity? Any QID for which Wikidata's Special:EntityData export returns an entity that isn't marked missing. That entity's label, description, aliases, and claims are extracted even if some individual claims (e.g. no founder on file) are empty.

What if I paste a full Wikidata URL instead of a QID? Both work. https://www.wikidata.org/wiki/Q95 and Q95 normalize to the same QID before lookup.

Why are some claim fields empty even when the entity is found? Only entities that actually have that property populated in Wikidata will return a value — e.g. many entities have no founder or headquarters claim at all. That's a gap in the source data, not a failure of the lookup.

Does this cover every Wikidata property? No. Wikidata entities can carry hundreds of raw property-ID claims. This actor resolves a curated, commonly-useful set (instance-of, inception date, official website, country, founder, headquarters, industry) rather than dumping every unlabeled property ID.

How does testRun work? Turn it on to process only the first 5 QIDs from your list — useful to confirm your input and column choices look right before running the full batch.

Should I use a proxy? Apify Proxy is enabled by default. Residential proxies are recommended if you're running high volumes, since this target has no browser fallback and getting blocked costs more than running slow and steady — keep maxConcurrency conservative for large batches.