# Wikipedia Contact Email Scraper (`neuro-scraper/wikipedia-contact-email-scraper`) Actor

Wikipedia Contact Email Scraper SD - Wikipedia Contact Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Wikipedia results by keyword, location and email domain - Wikipedia email extractor.

- **URL**: https://apify.com/neuro-scraper/wikipedia-contact-email-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

### Wikipedia Contact Email Scraper - emails cited in Wikipedia articles, honestly labelled

The Wikipedia Contact Email Scraper searches Google's public index of `wikipedia.org` and extracts email addresses that appear in the indexed result text.
Read this before your first run: **Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact.**
That distinction is the single most important thing to understand about the Wikipedia Contact Email Scraper.

Wikipedia is an encyclopedia, not a directory. Articles about organisations and institutes do not list a press inbox as a matter of style.
What they do contain are citations: a press release, an annual report, a government notice, a letter, an archived page. Those sources sometimes carry an address, and that address gets indexed with the article.

So a row from the Wikipedia Contact Email Scraper is usually **a third party's address quoted in a reference**, not the subject's official contact.
Treat it as a research lead to verify, never as a confirmed contact channel.

Our measured live run reflects that: 10 result blocks, 10 rows with identity data, 10 profile URLs and 6 unique emails.

### Who uses the Wikipedia Contact Email Scraper

Desk researchers, due-diligence analysts and journalists run the Wikipedia Contact Email Scraper while mapping an organisation, to see which addresses appear in the public record around it.
It is a paper-trail tool rather than a lead-generation tool.

| Audience | How they use the Wikipedia Contact Email Scraper |
|---|---|
| Desk and archival researchers | Trace which addresses appear in the cited sources for a topic |
| Due-diligence and OSINT analysts | Map the public paper trail around an organisation or institute |
| Journalists | Follow citations to a reachable source |
| Academic researchers | Identify institutional sources referenced in an article |
| Knowledge-base and data teams | Audit what contact data leaks into encyclopedic citations |
| Non-profit and policy researchers | Find referenced bodies working in a policy area |

### How the Wikipedia Contact Email Scraper works

The Wikipedia Contact Email Scraper never logs into Wikipedia, never uses the MediaWiki API and never opens an article in a browser.
There is no JavaScript rendering, no authentication and no cookie handling.

The run is a structured Google harvest:

1. Read the input: keywords, location, email domains and limits.
2. Build Google queries with the `site:` operator, for example `site:wikipedia.org institute contact "@gmail.com"`.
3. Fetch result pages through the **Apify GOOGLE_SERP proxy** with async `aiohttp` requests.
4. Parse each result block structurally by locating the `<h3>` title and the smallest surrounding block.
5. Extract emails from the block text with a domain-filtered regular expression.
6. Deduplicate globally and push each lead to the Apify dataset immediately.

Everything the Wikipedia Contact Email Scraper returns comes from publicly indexed search text: titles, snippets and site labels.
It does not read article wikitext, edit histories or user pages.

### Key features of the Wikipedia Contact Email Scraper

| Feature | What it does |
|---|---|
| Google `site:` scoping | Restricts every query to `wikipedia.org`, across language editions Google surfaces |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per modifier; base queries run first |
| Query modifiers | `email`, `contact`, `press`, `booking`, `submissions` by default |
| Email domain filtering | Keeps only addresses on your `customDomains` list |
| Global deduplication | One unique email per run across every query and page |
| Obfuscated address handling | Reads `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and full-width `＠` |
| Placeholder rejection | Filters `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same block |
| Structural block parsing | No dependence on Google CSS class names |
| Whole-page fallback parser | A markup change degrades to "emails without account details", not "no emails" |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried |
| Retries and re-queueing | Up to 3 attempts per page with exponential backoff and a fresh proxy session; failed queries re-queued once |
| Resumable state | Key-value store state keyed by an input hash, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Async concurrency | `asyncio` worker pool with a shared stop signal on `maxEmails` |
| Streaming dataset writes | Rows appear as they are found |

The Wikipedia Contact Email Scraper also logs pages fetched, blocked pages, retries and emails per page in the run summary.

### Input fields for the Wikipedia Contact Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["organisation", "institute"]` | Search terms describing the articles or subjects you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; `@` optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email","contact","press","booking","submissions"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

#### Example input for the Wikipedia Contact Email Scraper

```json
{
  "keywords": ["marine research institute", "heritage foundation", "organisation"],
  "location": "Portugal",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 60,
  "countryCode": "PT",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "press", "booking", "submissions"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Set `maxEmails` conservatively. Given how rarely Wikipedia publishes addresses, a Wikipedia Contact Email Scraper run usually ends because matches run out, not because the cap is reached.

### Output fields from the Wikipedia Contact Email Scraper

Every dataset item carries all fourteen fields.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or caption snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, for example `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

On Wikipedia the exposed handle is the article slug, so the Wikipedia Contact Email Scraper builds `profileUrl` as `https://en.wikipedia.org/wiki/{username}`.
That URL identifies the **article**, not the owner of the email.

#### Example output from the Wikipedia Contact Email Scraper

```json
[
  {
    "network": "Wikipedia",
    "keyword": "marine research institute",
    "query": "site:wikipedia.org \"marine research institute\" contact \"@gmail.com\" \"Portugal\"",
    "title": "Algarve Marine Research Institute - Wikipedia",
    "accountName": "Algarve_Marine_Research_Institute",
    "fullName": "Algarve Marine Research Institute",
    "username": "Algarve_Marine_Research_Institute",
    "profileUrl": "https://en.wikipedia.org/wiki/Algarve_Marine_Research_Institute",
    "url": "https://en.wikipedia.org/wiki/Algarve_Marine_Research_Institute",
    "description": "Cited press release lists enquiries to coastalsurvey.press@gmail.com",
    "email": "coastalsurvey.press@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T17:05:12.338Z"
  },
  {
    "network": "Wikipedia",
    "keyword": "heritage foundation",
    "query": "site:wikipedia.org \"heritage foundation\" email \"@yahoo.com\"",
    "title": "Douro Heritage Foundation - Wikipedia",
    "accountName": "Douro_Heritage_Foundation",
    "fullName": "Douro Heritage Foundation",
    "username": "Douro_Heritage_Foundation",
    "profileUrl": "https://en.wikipedia.org/wiki/Douro_Heritage_Foundation",
    "url": "https://en.wikipedia.org/wiki/Douro_Heritage_Foundation",
    "description": "Reference 14 quotes a 2019 newsletter signed douro.newsletter...",
    "email": "douro.newsletter@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T17:06:30.771Z"
  }
]
```

Both rows illustrate the pattern the Wikipedia Contact Email Scraper produces: the address came from a cited source, and the profile URL points at the article that cited it.
The second row is flagged `possiblyTruncated`, so it needs verification before any use.

### What results to expect from the Wikipedia Contact Email Scraper

Our measured live run returned 10 result blocks, 10 identity rows, 10 profile URLs and 6 unique emails.
Identity resolution is excellent because every article has a stable slug, but email density is moderate for a structural reason.

Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact.
Volume from the Wikipedia Contact Email Scraper varies with keywords, `customDomains`, `countryCode` and `location`, and no number is guaranteed.

### Tips for stronger Wikipedia Contact Email Scraper runs

Give the Wikipedia Contact Email Scraper the kind of body you want: "research institute", "foundation", "observatory", "heritage trust", "regional agency".
Those article types cite reports and press material far more often than biographies do.

Widen `customDomains` beyond free-mail; cited sources often use institutional or `.org` addresses.
Keep `expandQueries` on to work around Google's roughly 300-results-per-query ceiling, and do not expect concurrency to increase yield.

Researchers often pair this with the [Internet Archive Email Scraper](https://apify.com/neuro-scraper/internet-archive-email-scraper) for archived source material and the [Scribd Email Scraper](https://apify.com/leads-scraper/scribd-email-scraper) for reports and grey literature.

### Limitations of the Wikipedia Contact Email Scraper

- **Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact.** This is the dominant limitation and it affects how every row should be read.
- An address found this way may belong to a third party quoted in a source, not to the subject of the article.
- The Wikipedia Contact Email Scraper only finds pages whose email is **publicly visible in Google's index**; it does not read wikitext, references sections in full, or edit histories.
- Cited material can be old, so an address may be out of date.
- Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
- `possiblyTruncated: true` means Google's snippet ellipsis may have clipped the address; verify before use.
- `username` and `profileUrl` are only populated when a slug is exposed in the Google result, and that URL identifies the article rather than the address owner. Rows without a slug arrive with `username: null` and an empty `profileUrl`. This is a Google limitation, not a bug.
- The Actor requires the **Apify GOOGLE_SERP proxy** and cannot run without Apify proxy credentials.
- Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
- Results vary with keywords, domains and location; no volume is guaranteed.

### Ethics and responsible use

The Wikipedia Contact Email Scraper needs a clearer conscience than most, because of whose addresses it surfaces.
An email cited in a Wikipedia reference usually belongs to a **third party** - an author, a spokesperson, a signatory - who published it in a different context for a different purpose.

Verify who an address actually belongs to before you contact anyone, and never assume it is an organisation's official channel.
Use these leads for relevant, respectful correspondence: source verification, research enquiries, corrections and permissions.

Do not build marketing lists from third-party addresses lifted out of citations, and honour any opt-out immediately.
Respect GDPR and institutional norms, and check with your compliance or editorial team if you are unsure. This is not legal advice.

### Related Actors

The Wikipedia Contact Email Scraper shares its engine with every Actor below in the Content, Media, Research and Entertainment category.

| Actor | What it collects |
|---|---|
| [Wikipedia Email and Phone Number Scraper](https://apify.com/neuro-scraper/wikipedia-contact-email-and-phone-number-scraper) | Emails and phone numbers from Wikipedia |
| [Wikipedia Phone Number Scraper](https://apify.com/neuro-scraper/wikipedia-contact-phone-number-scraper) | Public phone numbers from Wikipedia |
| [ArtStation Email Scraper](https://apify.com/neuro-scraper/artstation-email-scraper) | Public contact emails from ArtStation |
| [arXiv Email Scraper](https://apify.com/leads-scraper/arxiv-email-scraper) | Public contact emails from arXiv |
| [Blogger Email Scraper](https://apify.com/neuro-scraper/blogger-email-scraper) | Public contact emails from Blogger |
| [Crunchyroll Email Scraper](https://apify.com/neuro-scraper/crunchyroll-email-scraper) | Public contact emails from Crunchyroll |
| [Digg Email Scraper](https://apify.com/neuro-scraper/digg-email-scraper) | Public contact emails from Digg |
| [Flipboard Email Scraper](https://apify.com/neuro-scraper/flipboard-email-scraper) | Public contact emails from Flipboard |
| [iHeartRadio Email Scraper](https://apify.com/neuro-scraper/iheartradio-email-scraper) | Public contact emails from iHeartRadio |
| [IMDb Email Scraper](https://apify.com/leads-scraper/imdb-email-scraper) | Public contact emails from IMDb |
| [Internet Archive Email Scraper](https://apify.com/neuro-scraper/internet-archive-email-scraper) | Public contact emails from Internet Archive |
| [iTunes Podcast Host Email Scraper](https://apify.com/leads-scraper/itunes-podcast-host-email-scraper) | Public contact emails from Apple Podcasts |
| [Netflix Shows Email Scraper](https://apify.com/neuro-scraper/netflix-shows-email-scraper) | Public contact emails from Netflix |
| [Rotten Tomatoes Email Scraper](https://apify.com/neuro-scraper/rotten-tomatoes-email-scraper) | Public contact emails from Rotten Tomatoes |
| [Scribd Email Scraper](https://apify.com/leads-scraper/scribd-email-scraper) | Public contact emails from Scribd |
| [Spotify Email Scraper](https://apify.com/leads-scraper/spotify-email-scraper) | Public contact emails from Spotify |
| [Spotify Playlist Email Scraper](https://apify.com/leads-scraper/spotify-playlist-email-scraper) | Public contact emails from Spotify |
| [TuneIn Email Scraper](https://apify.com/neuro-scraper/tunein-email-scraper) | Public contact emails from TuneIn |
| [WordPress Blog Email Scraper](https://apify.com/leads-scraper/wordpress-blog-email-scraper) | Public contact emails from WordPress.com |
| [ArtStation Email and Phone Number Scraper](https://apify.com/neuro-scraper/artstation-email-and-phone-number-scraper) | Emails and phone numbers from ArtStation |
| [arXiv Email and Phone Number Scraper](https://apify.com/neuro-scraper/arxiv-email-and-phone-number-scraper) | Emails and phone numbers from arXiv |
| [Blogger Email and Phone Number Scraper](https://apify.com/neuro-scraper/blogger-email-and-phone-number-scraper) | Emails and phone numbers from Blogger |
| [Crunchyroll Email and Phone Number Scraper](https://apify.com/neuro-scraper/crunchyroll-email-and-phone-number-scraper) | Emails and phone numbers from Crunchyroll |
| [Digg Email and Phone Number Scraper](https://apify.com/neuro-scraper/digg-email-and-phone-number-scraper) | Emails and phone numbers from Digg |
| [Flipboard Email and Phone Number Scraper](https://apify.com/neuro-scraper/flipboard-email-and-phone-number-scraper) | Emails and phone numbers from Flipboard |
| [iHeartRadio Email and Phone Number Scraper](https://apify.com/neuro-scraper/iheartradio-email-and-phone-number-scraper) | Emails and phone numbers from iHeartRadio |
| [IMDb Email and Phone Number Scraper](https://apify.com/neuro-scraper/imdb-email-and-phone-number-scraper) | Emails and phone numbers from IMDb |
| [Internet Archive Email and Phone Number Scraper](https://apify.com/neuro-scraper/internet-archive-email-and-phone-number-scraper) | Emails and phone numbers from Internet Archive |
| [Apple Podcasts Email and Phone Number Scraper](https://apify.com/neuro-scraper/itunes-podcast-host-email-and-phone-number-scraper) | Emails and phone numbers from Apple Podcasts |
| [Netflix Email and Phone Number Scraper](https://apify.com/neuro-scraper/netflix-shows-email-and-phone-number-scraper) | Emails and phone numbers from Netflix |
| [Rotten Tomatoes Email and Phone Number Scraper](https://apify.com/neuro-scraper/rotten-tomatoes-email-and-phone-number-scraper) | Emails and phone numbers from Rotten Tomatoes |
| [Scribd Email and Phone Number Scraper](https://apify.com/neuro-scraper/scribd-email-and-phone-number-scraper) | Emails and phone numbers from Scribd |
| [Spotify Email and Phone Number Scraper](https://apify.com/neuro-scraper/spotify-email-and-phone-number-scraper) | Emails and phone numbers from Spotify |
| [Spotify Email and Phone Number Scraper](https://apify.com/neuro-scraper/spotify-playlist-email-and-phone-number-scraper) | Emails and phone numbers from Spotify |
| [TuneIn Email and Phone Number Scraper](https://apify.com/neuro-scraper/tunein-email-and-phone-number-scraper) | Emails and phone numbers from TuneIn |
| [ArtStation Phone Number Scraper](https://apify.com/neuro-scraper/artstation-phone-number-scraper) | Public phone numbers from ArtStation |
| [arXiv Phone Number Scraper](https://apify.com/neuro-scraper/arxiv-phone-number-scraper) | Public phone numbers from arXiv |
| [Blogger Phone Number Scraper](https://apify.com/neuro-scraper/blogger-phone-number-scraper) | Public phone numbers from Blogger |
| [Crunchyroll Phone Number Scraper](https://apify.com/neuro-scraper/crunchyroll-phone-number-scraper) | Public phone numbers from Crunchyroll |
| [Digg Phone Number Scraper](https://apify.com/neuro-scraper/digg-phone-number-scraper) | Public phone numbers from Digg |
| [Flipboard Phone Number Scraper](https://apify.com/neuro-scraper/flipboard-phone-number-scraper) | Public phone numbers from Flipboard |
| [iHeartRadio Phone Number Scraper](https://apify.com/neuro-scraper/iheartradio-phone-number-scraper) | Public phone numbers from iHeartRadio |

### FAQ about the Wikipedia Contact Email Scraper

#### How many results should I expect from the Wikipedia Contact Email Scraper?

Our measured live run returned 10 result blocks, 10 identity rows, 10 profile URLs and 6 unique emails.
Wikipedia articles rarely publish contact addresses, so moderate email volume with excellent identity data is the normal pattern.

#### Does the Wikipedia Contact Email Scraper return official organisation contacts?

Usually not. Most rows carry an email cited in a reference rather than an official contact, so verify ownership before contacting anyone.

#### Whose address am I actually looking at?

Often a third party quoted in a cited source - an author, spokesperson or signatory. The Wikipedia Contact Email Scraper reports where the address was found, not who controls it.

#### Does the Wikipedia Contact Email Scraper use the MediaWiki API?

No. It never uses the API, never logs in and never opens an article. All data comes from publicly indexed Google results.

#### Does the Wikipedia Contact Email Scraper read the full references section?

No. It reads only Google's indexed result text, so it sees whatever fragment Google surfaced.

#### Why does `profileUrl` point at an article?

Because the exposed handle is the article slug, and `https://en.wikipedia.org/wiki/{username}` is the canonical URL for it. It identifies the article, not the email owner.

#### Can I target a country with the Wikipedia Contact Email Scraper?

Yes. Set `countryCode` to a two-letter code such as `US`, `GB` or `PT`, and optionally add a `location` phrase.

#### Which email domains does the Wikipedia Contact Email Scraper collect?

Only those in `customDomains`. The default is `@gmail.com` and `@yahoo.com`, and the leading `@` is optional.

#### What does `possiblyTruncated` mean?

Google's snippet ellipsis touched the address, so it may be incomplete. Verify those rows before use.

#### Could a Wikipedia Contact Email Scraper address be out of date?

Yes. Citations can be years old, so an address quoted in a reference may no longer be monitored.

#### Does the Wikipedia Contact Email Scraper handle obfuscated addresses?

Yes. It normalises `[at]`/`[dot]` spellings, `(at)` forms, spaced `@`, spaced `.com`, zero-width characters and the full-width `＠`.

#### Do I need Apify proxy access?

Yes. The Wikipedia Contact Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

#### Is there a free-plan cap?

Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

### Leave a review

If the Wikipedia Contact Email Scraper saved you time, please leave a star rating and a short
review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions about the Wikipedia Contact Email Scraper, feature requests or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Wikipedia accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Wikipedia.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "organisation",
    "institute"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "press",
    "booking",
    "submissions"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Wikipedia Contact Email Scraper, stored in the run's default dataset.

# 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 = {
    "keywords": [
        "organisation",
        "institute"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "press",
        "booking",
        "submissions"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/wikipedia-contact-email-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 = {
    "keywords": [
        "organisation",
        "institute",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "press",
        "booking",
        "submissions",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/wikipedia-contact-email-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 '{
  "keywords": [
    "organisation",
    "institute"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "press",
    "booking",
    "submissions"
  ]
}' |
apify call neuro-scraper/wikipedia-contact-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/wikipedia-contact-email-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/ECigzrmdOJQpbTaQs/builds/B8CEnZT7XA8K5BHaO/openapi.json