Bluesky Followers Scraper

Export public Bluesky followers and following lists from handles, profile URLs or DIDs. Get graph relationships and available profile details for audience research, community analysis and your own comparison workflows. No Bluesky login is required.

Quick start

Open the Actor, paste this input and start a small export:

{
  "handles": ["bsky.app"],
  "mode": "followers",
  "maxItemsPerProfile": 20,
  "includeProfileDetails": true
}

When the run finishes, open its dataset to review the related accounts. Each row represents one relationship, not a historical change in follower count.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

• Public followers, following accounts or both directions.
• Source and related-account handles and DIDs on each graph record.
• Available profile details, including descriptions, avatars, counters and labels.
• Cursor checkpoints for exports that stop at their safe work limit.

Who is it for?

• Community managers and creators researching the public accounts around a community.
• Researchers and journalists mapping relationships between public profiles.
• Analysts and developer-relations teams exporting account lists for further review or enrichment.

Input settings

Field	Description
handles	Up to 100 unique Bluesky handles, profile URLs or DIDs.
mode	followers, following or both.
maxItemsPerProfile	Maximum records per source and direction, up to 5,000.
includeProfileDetails	Include available bio, avatar, counters, labels and verification data.
sinceCursor	Resume one source and one direction. Leave empty for a new export.
requestDelayMs	Delay between graph-page requests. Keep the default for larger exports.
maxRuntimeSeconds	Optional 60–270 second work cap with a resumable checkpoint.

Following recipe: use "mode": "following" to export accounts a profile follows. Use "mode": "both" for both directions. Each direction has its own per-profile record limit.

Output data

Each dataset item is one public graph relationship. Optional profile fields can be absent or null.

Fields	Meaning
sourceHandle, sourceDid, mode	Source profile and relationship direction.
profileDid, profileHandle, displayName	Related profile identity and available display name.
description, avatarUrl	Available profile biography and avatar.
followersCount, followsCount, postsCount	Counters returned for the related profile.
createdAt, indexedAt	Profile timestamps when available.
verificationStatus, labels	Public verification and label payloads.
cursorPage, scrapedAt	Page cursor and collection timestamp.

Illustrative shape only. These identifiers and values are placeholders, not observed account data:

{
  "sourceHandle": "bsky.app",
  "sourceDid": "did:plc:source-example",
  "mode": "followers",
  "profileDid": "did:plc:profile-example",
  "profileHandle": "example.bsky.social",
  "displayName": "Example profile",
  "followersCount": 12,
  "scrapedAt": "2026-10-22T00:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged once after input validation, before source lookups. A valid run can incur this charge even if a later lookup fails or returns no records.

The item event is charged per follower/following record saved. Failed lookups and malformed records are not saved as graph records.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with one account and 20 records. Review the output before increasing limits.
• Choose one direction when possible. Use both only when you need both relationship lists.
• Use handles or DIDs for simple inputs. Profile URLs are also accepted.
• Keep exports bounded. Split large source lists into smaller runs and retain cursors for continuation.

Limits and caveats

• Only public data returned by Bluesky is available. The Actor does not retrieve private or login-only information and is not affiliated with Bluesky.
• Profile details and counters may be unavailable. A graph export is a snapshot, not a complete account history.
• Large exports can stop before the platform timeout. Saved rows remain available, and PENDING_WORK identifies remaining source/direction/cursor work.
• RUN_SUMMARY lists warnings and source-level errors. Mixed batches preserve successful rows. If every source fails, the current implementation fails the run rather than presenting an unknown result as a valid empty list.
• Public social graphs can contain personal data. Collect only what your lawful use case needs and follow applicable platform terms.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~bluesky-followers-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"handles":["bsky.app"],"mode":"followers","maxItemsPerProfile":20}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/bluesky-followers-scraper').call({
  handles: ['bsky.app'],
  mode: 'followers',
  maxItemsPerProfile: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/bluesky-followers-scraper').call(run_input={
    'handles': ['bsky.app'],
    'mode': 'followers',
    'maxItemsPerProfile': 20,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Bluesky Followers Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Bluesky Followers Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/bluesky-followers-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Bluesky Followers Scraper by Fetch Cat, or give it the identifier fetch_cat/bluesky-followers-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• Collect 20 public followers of bsky.app and organize their handles and available biographies in a table.
• Export 30 accounts followed by apify.com and group their available profile descriptions by topic.
• Retrieve up to 20 followers and 20 following accounts for bsky.app, then compare the returned handles for overlap.

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability. This Actor uses pay-per-event pricing, so do not assume it supports direct per-request MCP payments. The prepaid-token API route is the relevant alternative.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Do I need a Bluesky account?

No. The Actor collects public graph records without login cookies.

Can I export both followers and following?

Yes. Set mode to both. Each direction can save up to maxItemsPerProfile records per source.

How do I resume an interrupted export?

Read PENDING_WORK. Start a new run with its source handle, recorded direction and cursor in sinceCursor. Resume only one source and direction at a time. For both, resume the two directions separately.

Why are some profile details missing?

The Actor can only return fields available from Bluesky. Enable includeProfileDetails when you need the available counters and profile metadata, but do not assume every field exists for every account.

Related Actors

• Bluesky Profile Feed Scraper — Export public profile feeds alongside graph records.
• Bluesky Actor Search Scraper — Find public accounts before choosing graph-export targets.
• Bluesky Scraper — Explore broader Bluesky collection workflows.
• Mastodon Posts & Profiles Scraper — Research public profiles on another decentralized social platform.
• X / Twitter Posts Scraper — Collect public post data for cross-platform research.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave an honest review from the Actor page using its review controls. Your feedback helps others choose the right tool and helps us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥