# Wikidata Entity Search Scraper (`parseforge/wikidata-entity-search-scraper`) Actor

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

- **URL**: https://apify.com/parseforge/wikidata-entity-search-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Education, Automation
- **Features:** Limited permissions
- **Stats:** 5 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $14.00 / 1,000 result items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner-v4.webp)](https://apify.com/parseforge?fpr=vmoqkp)

### 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:

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

A larger pull:

```json
{
 "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](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [Wikidata Entity Search Scraper](https://apify.com/parseforge/wikidata-entity-search-scraper?fpr=vmoqkp).
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](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) 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:

```bash
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](https://apify.com/parseforge?fpr=vmoqkp) 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.

# Actor input Schema

## `maxItems` (type: `integer`):

How many entities to collect per run.

## `query` (type: `string`):

Term to search Wikidata entities (people, places, things, concepts).

## `language` (type: `string`):

Wikidata search language code.

## `entityType` (type: `string`):

Search items (Q-entities) or properties (P-entities).

## `fetchClaims` (type: `boolean`):

If checked, fetches full statements/claims, sitelinks, and aliases per entity (1 extra API call per entity).

## Actor input object example

```json
{
  "maxItems": 10,
  "query": "tesla",
  "language": "en",
  "entityType": "item",
  "fetchClaims": true
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 10,
    "query": "tesla",
    "language": "en",
    "entityType": "item"
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/wikidata-entity-search-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxItems": 10,
    "query": "tesla",
    "language": "en",
    "entityType": "item",
}

# Run the Actor and wait for it to finish
run = client.actor("parseforge/wikidata-entity-search-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 10,
  "query": "tesla",
  "language": "en",
  "entityType": "item"
}' |
apify call parseforge/wikidata-entity-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/wikidata-entity-search-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/WtxXGfWDArwmiTSoL/builds/cWzOuI34FQnTUZH6p/openapi.json