ParseForge Scrapers

Wikidata Entity Search Scraper

parseforge/wikidata-entity-search-scraper

EducationAutomationOther

Scrapes Wikidata entity search results by term, language, and type. Returns QID, label, description, aliases, and optional full claims and sitelinks.

Run this scraper See the API call
Total users
4
Monthly active
1
Total runs
134
Bookmarked
0
Rating
Not rated yet
Last modified
12 days ago

Overview

ParseForge

Wikidata Entity Search Scraper

Scrape Wikidata entity search results for any term, in 20 languages, up to a million entities per run. Every entity comes with its QID, label, description, aliases, and optional full claims and sitelinks. No API key or login. Export to CSV, JSON, Excel, or XML.

Wikidata's official API needs a user agent, rate limits, and manual pagination. This reads the public entity search endpoint directly, filtered by language and entity type, and returns each match in one fixed schema. It is the fastest way to build a knowledge graph dataset from Wikidata without writing code.

Who uses it What they scrape Wikidata for
Knowledge graph engineers Enriching internal entities with Wikidata QIDs and descriptions
Market researchers Building lists of companies, people, or products from Wikidata
SEO analysts Collecting entity labels and aliases for semantic search optimization
Data journalists Gathering structured facts about a topic for a story
Academic researchers Creating datasets of concepts, places, or works for analysis

What it does

This Actor collects Wikidata entities by search term, language, and type, and returns each one as a flat row with its QID, label, description, aliases, and optional full claims and sitelinks.

  • ๐Ÿ” Search by term: enter any entity name or phrase, from 'tesla' to 'quantum physics'.
  • ๐ŸŒ 20 languages: search in English, Spanish, French, German, Japanese, Chinese, and more.
  • ๐Ÿ“Š Entity types: filter to items (Q-entities) or properties (P-entities).
  • ๐Ÿ“ฆ Full claims: optionally fetch statements, sitelinks, and aliases for each entity.
  • โšก Up to 1M entities: set maxItems to collect as many results as you need.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Wikidata data

๐Ÿ“ˆ Build a knowledge graph.

A data engineer runs the Actor with a list of company names and fetches full claims to link internal records to Wikidata QIDs and external identifiers.

๐Ÿ”Ž Enrich SEO entities.

An SEO analyst searches for a topic in multiple languages and exports labels and aliases to optimize content for semantic search.

๐Ÿ“ฐ Gather facts for a story.

A journalist searches for a person or event and collects descriptions, aliases, and sitelinks to verify facts and find sources.

๐ŸŽ“ Create a research dataset.

An academic researcher searches for concepts in a domain and exports QIDs and descriptions to build a corpus for analysis.

๐Ÿข Enrich CRM records.

A sales operations manager searches for company names and fetches full claims to append industry, location, and identifiers to CRM entries.

Why choose this scraper

What you get
No API key Uses the public Wikidata search endpoint, no registration or OAuth.
Fixed schema Every entity returns the same flat fields, ready for CSV or database import.
Multilingual Search in 20 languages and get labels and descriptions in that language.
Full claims Optionally fetch statements, sitelinks, and aliases with one extra call per entity.
Scalable Collect up to 1,000,000 entities per run, with automatic pagination.

How it compares

This Actor focuses on flexible Wikidata entity search with language and type filters, while the competitors below target specific use cases like PEP screening or basic entity listing.

Feature ParseForge PEP Screening - OpenSanctions + Wikidata + National Registries Wikidata Entities Scraper - Knowledge Graph Search
Search by arbitrary term Yes Not listed Yes
Language filter (20 languages) Yes Not listed Not listed
Entity type filter (item/property) Yes Not listed Not listed
Fetch full claims and sitelinks Yes Not listed Not listed
PEP screening for AML/KYC Not listed Yes Not listed
Up to 1M entities per run Yes Not listed Not listed

Configure the run

Drive the Actor from a search term, language, and entity type, and optionally fetch full claims for each entity. Filters run as each result is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
 "maxItems": 10,
 "query": "tesla",
 "language": "en",
 "entityType": "item"
}

A larger pull:

{
 "maxItems": 200,
 "query": "tesla",
 "language": "en",
 "entityType": "item"
}

Pricing

Pay-per-result: $0.01867 per result collected. You pay only for the results written to your dataset.

Results collected Approximate cost
100 results $1.87
1,000 results $18.67
10,000 results $186.70

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

  1. Create a free Apify account with $5 in credit.
  2. Open the Wikidata Entity Search Scraper.
  3. Set your inputs and any filters, then click Start.
  4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Wikidata through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/wikidata-entity-search-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check your search term. Wikidata search is exact on labels and aliases, so try a broader term or a different language. Also ensure entityType matches what you expect, e.g., 'item' for things, 'property' for attributes.

Why is the run slow?

If 'fetch full claims' is enabled, the Actor makes an extra API call per entity. Disable it for faster runs if you only need basic fields.

Why are some fields empty?

Not all entities have descriptions, aliases, or claims. Empty fields are normal. Use the full claims option to get more data when available.

Why did I get fewer results than maxItems?

The Actor stops when Wikidata has no more results for your query. Try a more general search term or a different language.

Why do I see a 429 error?

Wikidata rate limits may be hit on very large runs. The Actor retries automatically, but you can reduce maxItems or run during off-peak hours.

FAQ

Question Answer
What is Wikidata? Wikidata is a free and open knowledge base by the Wikimedia Foundation. It stores structured data about entities like people, places, concepts, and works, each with a unique QID.
Do I need an API key or login? No. The Actor uses the public Wikidata search endpoint, so you only need an Apify account to run it.
What is a QID? A QID is the unique identifier for an item in Wikidata, like Q42 for Douglas Adams. Properties have PIDs, like P31 for 'instance of'.
What is the difference between items and properties? Items (Q-entities) are things like people, places, or concepts. Properties (P-entities) are relationships or attributes, like 'date of birth' or 'country'.
What does 'fetch full claims' do? When enabled, the Actor makes one extra API call per entity to fetch all statements, sitelinks, and aliases. This gives you complete data but increases runtime.
How many entities can I collect? You can set maxItems up to 1,000,000. The Actor will paginate through search results until it reaches that number or no more results exist.
Which languages are supported? 20 languages: English, Spanish, French, German, Italian, Portuguese, Dutch, Russian, Japanese, Chinese, Korean, Arabic, Hindi, Turkish, Polish, Swedish, Finnish, Danish, Norwegian, and Czech.
Can I search for multiple terms at once? The Actor accepts one search term per run. To search multiple terms, run the Actor multiple times or use Apify's scheduler or API to loop over a list.
What output formats are available? You can export results as CSV, JSON, Excel, or XML from the Apify dataset.
Is this the same as the Wikidata API? Yes, it uses the official Wikidata search API under the hood, but handles pagination, rate limits, and schema normalization for you.
Can I get data in a language other than English? Yes, set the language parameter to any of the 20 supported codes. Labels and descriptions will be returned in that language when available.
What is the cost? The Actor runs on Apify's platform. You pay only for the compute resources used, with a free monthly tier available.

Related actors

Browse the full ParseForge collection for more scrapers.

๐Ÿ†˜ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

โš ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Wikimedia Foundation, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

Input

FieldTypeWhat it doesDefault
maxItems integer How many entities to collect per run. 10
query string Term to search Wikidata entities (people, places, things, concepts). tesla
language string (20 options) Wikidata search language code. en
entityType string (2 options) Search items (Q-entities) or properties (P-entities). item
fetchClaims boolean If checked, fetches full statements/claims, sitelinks, and aliases per entity (1 extra API call per entity). true

Pricing

from $14.00 per 1,000 results

Charged forWhat it isPrice each
Result item Charged per record successfully returned in the dataset. $0.014 to $0.01867

Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.

API

One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.

POST ยท run and get results
curl -X POST "https://api.apify.com/v2/acts/parseforge~wikidata-entity-search-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "helloWorld": 123
  }'

Examples

Input that runs as-is.

input.json
{
  "helloWorld": 123
}

Reviews

No reviews yet. Be the first.

Issues

We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.

Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.

Related scrapers

Run Wikidata Entity Search Scraper on Apify All scrapers