# Bluesky Email Scraper (`leads-scraper/bluesky-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/bluesky-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-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

### Bluesky Email Scraper

### Bluesky Email Scraper — Extract Public Contact Emails from bsky.app

The **Bluesky Email Scraper** finds publicly indexed contact emails belonging to Bluesky accounts and delivers them as clean, structured data.

You give it keywords such as `founder` or `developer`, choose the email domains you care about, and the Bluesky Email Scraper returns a dataset of leads with account names, handles, bios and profile URLs.

Bluesky grew out of the AT Protocol into a home for developers, journalists, indie founders, scientists, illustrators and open-source maintainers. Many of them put a working email straight into their bio.

The Bluesky Email Scraper is built to surface exactly those bios. It is a Bluesky email extractor for lead generation, creator outreach, recruiting and partnership research — not a follower harvester and not an API client.

**Important:** this Bluesky Email Scraper never logs into Bluesky, never touches the AT Protocol API, and never opens `bsky.app` itself. Every record comes from publicly indexed Google search results.

***

### Key Features of the Bluesky Email Scraper

The feature set below reflects what the Bluesky Email Scraper genuinely does — no invented capabilities, no marketing fiction.

| Feature | What it means in practice |
|---|---|
| Google `site:` search collection | The Bluesky Email Scraper queries Google restricted to `bsky.app`, so only Bluesky pages are parsed |
| Query expansion | Each keyword × domain pair is searched in several phrasings: base, quoted, `intitle:`, plus one variant per query modifier |
| Domain-filtered extraction | Only emails ending in your `customDomains` list are kept |
| Global deduplication | One email appears once across every query and every page of the run |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders like `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Discards a hit that is only the tail of another email in the same result block |
| Structural HTML parsing | Locates the `<h3>` title then the smallest surrounding block — it does not depend on Google's CSS class names |
| Whole-page fallback parser | If Google's markup changes, the run degrades to "emails without account metadata" rather than "no emails" |
| Concurrency | An `asyncio` worker pool runs several queries in parallel with a shared stop signal on `maxEmails` |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not silently counted as empty |
| Blocked-query requeue | Failed or blocked queries are re-queued once at the end of the run |
| Resumable state | Progress is stored in the key-value store keyed by a hash of your input, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Streaming dataset writes | Each lead is pushed to the Apify dataset the moment it is found |
| Run summary | Logs pages fetched, blocked pages, retries and emails per page |

***

### How the Bluesky Email Scraper Works

The Bluesky Email Scraper pipeline is short and deliberately transparent. There is no browser, no JavaScript rendering, no authentication and no cookies.

**1. Read input.** The Bluesky Email Scraper loads your keywords, optional location, email domains and limits.

**2. Build queries.** It composes Google queries with the `site:` operator, for example `site:bsky.app founder "@gmail.com" "Berlin"`.

**3. Fetch search results.** Pages are requested asynchronously with `aiohttp` through the Apify **GOOGLE\_SERP** proxy, with retry logic and proxy rotation on every attempt.

**4. Parse result blocks.** For each result the Bluesky Email Scraper finds the `<h3>` title, walks up to the smallest enclosing block, and reads the title, site label and snippet.

**5. Extract and normalise emails.** A domain-filtered regex pulls addresses out of the block text, then normalisation and the junk filter clean them up.

**6. Deduplicate and push.** Every unique email is written to the dataset immediately, so you can start exporting mid-run.

Because base queries run first, the earliest rows the Bluesky Email Scraper writes are usually the highest-signal ones.

***

### What Data Does the Bluesky Email Scraper Extract?

The Bluesky Email Scraper produces one dataset item per unique email, and every item carries the same 14 fields.

Alongside the address itself you get the account label Google printed, a parsed display name, the handle when Bluesky exposes one, a canonical `bsky.app` profile link, and the bio snippet the email came from.

You also get full provenance: the keyword and the exact Google query that produced the lead, plus a UTC timestamp.

That provenance matters. It lets you see which keyword is actually productive for your niche and retire the ones that are not.

Nothing outside these 14 fields is collected. The Bluesky Email Scraper does not touch follower counts, private data or anything behind a login.

***

### Bluesky Email Scraper Input Schema

Every field below is taken verbatim from the Bluesky Email Scraper input schema.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["founder", "developer"]` | Search terms describing the Bluesky accounts you want (niche, job title, industry) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are collected; the leading `@` is optional |
| `maxEmails` | integer (1–10000) | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (`US`, `GB`, `DE`…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair with several phrasings |
| `queryModifiers` | array | `["email", "contact", "inquiries", "hire", "work with me"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer (1–50) | `30` | Page cap per query |
| `maxConcurrency` | integer (1–20) | `5` | How many queries run in parallel |

#### JSON input example

```json
{
  "keywords": ["indie game developer", "open source maintainer", "tech journalist"],
  "location": "Berlin",
  "customDomains": ["@gmail.com", "@proton.me"],
  "maxEmails": 300,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "inquiries", "hire", "work with me"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Bluesky Email Scraper Output Schema

Every dataset item produced by the Bluesky Email Scraper contains all 14 fields below.

| 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 (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when Bluesky 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 post snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain (e.g. `@gmail.com`) |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

#### JSON output example

```json
{
  "network": "Bluesky",
  "keyword": "indie game developer",
  "query": "site:bsky.app indie game developer \"@gmail.com\" \"Berlin\"",
  "title": "Maya Okonkwo (@maya.dev.bsky.social) — Bluesky",
  "accountName": "maya.dev.bsky.social",
  "fullName": "Maya Okonkwo",
  "username": "maya.dev.bsky.social",
  "profileUrl": "https://bsky.app/profile/maya.dev.bsky.social",
  "url": "https://bsky.app/profile/maya.dev.bsky.social",
  "description": "Indie game dev in Berlin. Pixel art, Godot, devlogs. Press kits and collabs: maya.okonkwo.dev@gmail.com",
  "email": "maya.okonkwo.dev@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:42:17Z"
}
```

***

### How to Use the Bluesky Email Scraper

**Step 1 — open the Actor.** Launch the [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) on the Apify platform.

**Step 2 — enter keywords.** Be specific. `Godot developer` and `climate scientist` beat `tech` every time on Bluesky.

**Step 3 — pick your email domains.** Start with `@gmail.com`. Add `@proton.me`, `@outlook.com` or `@hey.com` if your audience skews privacy-minded, as much of Bluesky does.

**Step 4 — set `maxEmails` and run.** Leave `expandQueries` on so query expansion works around Google's per-query result cap.

**Step 5 — export.** Download the Bluesky Email Scraper dataset as JSON, CSV, XLSX or feed it straight into your CRM through the Apify API.

You can also schedule a weekly run so new bios entering Google's index are picked up automatically.

If you want the same workflow on another network, the [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) is the closest sibling — Mastodon and Bluesky share a large slice of the same developer and journalist crowd.

***

### Use Cases for the Bluesky Email Scraper

| Use case | How the Bluesky Email Scraper helps |
|---|---|
| Developer tool marketing | Find engineers and maintainers who publish a contact address in their bio |
| Technical recruiting | Build sourcing lists of developers by stack keyword and location |
| Creator partnerships | Reach illustrators, writers and podcasters directly instead of via DM requests |
| Journalist and PR outreach | Assemble contact lists of reporters covering a specific beat |
| Newsletter growth | Identify writers open to cross-promotion or guest pieces |
| SaaS lead generation | Collect founder emails filtered by niche keyword |
| Community building | Contact organisers and hosts running Bluesky-native communities |
| Market research | Study how a niche describes itself, using the `description` snippets |
| CRM enrichment | Match handles and profile URLs to records you already own |
| Academic outreach | Reach scientists and researchers who moved to Bluesky from X |

Bluesky's audience is unusually technical and unusually open about contact details, which is why keyword-driven contact discovery works well here.

In every one of these scenarios the Bluesky Email Scraper does the tedious part — reading thousands of search results — and leaves the judgement to you.

***

### Why Choose This Bluesky Email Scraper

**It is honest about its source.** The Bluesky Email Scraper reads Google's public index. Nothing more, nothing hidden.

**It is resilient.** Structural parsing plus a whole-page fallback means a Google layout change degrades the Bluesky Email Scraper's output quality instead of breaking the crawler.

**It is resumable.** Migrations and aborts do not cost you a run; state is keyed by a hash of your input.

**It is precise.** Domain filtering, boundary-correct matching, obfuscation handling and the junk filter keep noise out of your dataset.

**It is part of a family.** The same engine powers dozens of sibling Actors, including the [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) for accounts that never left Twitter and the [GitHub-adjacent developer crowd you can also reach through the Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper).

***

### Limitations

These are real constraints. Read them before you set expectations.

- **Only publicly indexed emails.** If an address is not visible in Google's index, the Bluesky Email Scraper cannot find it. Private data is never accessed.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most. Query expansion exists precisely to work around this, so keep `expandQueries` on.
- **`possiblyTruncated`.** When Google's snippet ellipsis touches an address, the flag is set to `true`. Verify those rows before sending anything.
- **Apify GOOGLE\_SERP proxy required.** The Actor cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
- **`username` and `profileUrl` availability.** These are only populated when Google's result exposes a handle. Some rows will have `accountName` and `fullName` but an empty `username` and `profileUrl`. That is a Google limitation, not a bug.
- **No guaranteed volume.** Results vary with keywords, domains and location.

Nothing here is affiliated with, endorsed by or officially supported by Bluesky.

***

### Related Actors

| Actor | What it collects |
|---|---|
| [Bluesky Email and Phone Number Scraper](https://apify.com/leads-scraper/bluesky-email-and-phone-number-scraper) | Emails and phone numbers from Bluesky |
| [Bluesky Phone Number Scraper](https://apify.com/leads-scraper/bluesky-phone-number-scraper) | Public phone numbers from Bluesky |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### Bluesky Email Scraper Example Run

A small agency wants to pitch a developer-tools client to indie engineers on Bluesky.

They run the Bluesky Email Scraper with `keywords: ["rust developer", "devtools founder"]`, `customDomains: ["@gmail.com", "@proton.me"]` and `maxEmails: 250`.

Query expansion turns two keywords into a dozen phrasings, the Bluesky Email Scraper paginates through Google, and the dataset fills with handles, bios and addresses.

They sort by `possiblyTruncated`, drop the flagged rows, and hand a clean CSV to their outreach tool. Total setup time: under five minutes.

***

### Bluesky Email Scraper FAQ

#### Does the Bluesky Email Scraper log into Bluesky?

No. It never logs in, never uses the AT Protocol API and never opens `bsky.app`. All data comes from publicly indexed Google search results.

#### Where do the emails actually come from?

From Google result titles, site labels and snippets for pages on `bsky.app` — typically bios where the account owner published a contact address themselves.

#### Is this a Bluesky email extractor or a full profile scraper?

It is a Bluesky email extractor. It returns the 14 fields listed above and nothing else — no follower counts, no post history, no engagement metrics.

#### Do I need an Apify proxy?

Yes. The Bluesky Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### How many emails can the Bluesky Email Scraper collect per run?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by your `maxEmails` value and what Google has indexed.

#### Why is `username` empty on some rows?

Because Google did not expose a handle in that result. Those rows still carry `accountName`, `fullName` and the bio snippet. It is a Google limitation, not a scraper defect.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the email, so the address may be cut off. Verify those rows before sending.

#### Should I leave query expansion enabled?

Yes. Google caps a single query at roughly 300 results, and expansion is how the Bluesky Email Scraper reaches past that ceiling.

#### Can I filter to a specific email domain?

Yes — `customDomains` accepts any list, with or without the leading `@`. Only matching addresses are kept, and boundary-correct matching prevents false hits like `@gmail.company`.

#### Can I restrict results to one country?

Set `countryCode` to a two-letter code and optionally add a `location` phrase. Both narrow the search; neither guarantees geographic accuracy.

#### Does the Bluesky Email Scraper deduplicate?

Yes, globally. An email appears once per run no matter how many queries or pages surfaced it.

#### What happens if a Bluesky Email Scraper run is interrupted?

Progress is saved in the key-value store, keyed by a hash of your input, and flushed on `PERSIST_STATE`, `MIGRATING` and `ABORTING`. Restarting resumes rather than starting over.

#### Can I run it on a schedule?

Yes. Apify schedules work normally, and global deduplication within each run keeps the output tidy.

#### Is this affiliated with Bluesky?

No. The Bluesky Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Bluesky.

#### How should I use the results responsibly?

Follow GDPR, CAN-SPAM and any other law that applies to you. Publicly visible does not mean consent to bulk marketing — keep outreach relevant and honour opt-outs.

***

### Leave a review

If the Bluesky 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, bug reports or a custom build request? Email **neurodata.apify@gmail.com** and include your run ID so the Bluesky Email Scraper logs can be checked quickly.

# Actor input Schema

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

Search terms describing the Bluesky 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 Bluesky.

## `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": [
    "founder",
    "developer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Bluesky 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": [
        "founder",
        "developer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/bluesky-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": [
        "founder",
        "developer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "inquiries",
        "hire",
        "work with me",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/bluesky-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": [
    "founder",
    "developer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "inquiries",
    "hire",
    "work with me"
  ]
}' |
apify call leads-scraper/bluesky-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/bluesky-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/Dkl6qxXsN35c8pTb7/builds/UErvaZqHbGoHTN5kz/openapi.json