Bluesky Profile Feed Scraper

Export public Bluesky profile metadata and recent author-feed posts from handles or DIDs. Bluesky Profile Feed Scraper saves separate profile and post rows with account metrics, post text, engagement counts and Bluesky links—without a Bluesky login.

Quick start

1. Enter one or more public handles or DIDs in actors.
2. Choose a small post limit, then start the Actor.
3. Inspect the dataset and export JSON, CSV or Excel from Apify.

{
  "actors": ["bsky.app"],
  "maxPostsPerActor": 20,
  "includeReplies": false,
  "includeReposts": false
}

Each available account adds one profile row plus up to the requested number of matching posts. Use maxPostsPerActor: 0 for profiles only. This is a recent-feed sample, not a complete historical archive.

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.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Save Bluesky public profile counts without posts
• Collect Bluesky repost-inclusive feed samples
• Monitor multiple Bluesky brand accounts

What you get

Data	Useful for
Profile names, bios, avatars and available follower/following/post counts	Account enrichment and profile reporting
Recent post text, URLs, timestamps and available engagement counts	Social listening, announcement exports and downstream summaries
Optional replies and reposted feed items, with available provenance	Feed context and creator activity research
Public embed objects and labels when returned	Media/link references and downstream analysis

The Actor looks up named accounts. It does not search post keywords, collect follower lists, download media files or fetch full reply threads. It preserves the upstream feed order rather than sorting by engagement.

Who is it for?

• Social and community teams reviewing recent activity from a known list of public accounts.
• Researchers and journalists collecting account profiles and a bounded sample of recent posts.
• Data teams preparing profile reports or post exports for their own analysis.

Account and feed workflows

• Prepare a profile-only report. Supply handles or DIDs and set maxPostsPerActor to zero. Use the profile rows for available bios and follower, following or post counts. Retain actorDid with each export if you plan to compare snapshots in your own system.
• Review a recent announcement sample. Collect a few posts from a named account, leaving replies and reposts off when you want that narrower view. Review post text, timestamps and source links, then ask your assistant to summarize the returned posts. The Actor does not search post keywords, fetch full history or rank results by engagement.
• Understand repost context. Enable reposts when you need to see shared material in the recent feed. Compare the requested account with authorHandle and the available repost provenance so you do not attribute someone else's text to that account. The reply filter still applies, and complete conversation threads are not collected.

Profile and post rows share a dataset. Use recordType to separate them, actorDid for profile comparisons and uri for post comparisons in your downstream workflow. The Actor does not maintain history or detect changes for you.

Input settings

Setting	JSON key	Summary
Handles or DIDs	actors	Required list. Use handles or DIDs, not profile URLs.
Maximum posts per account	maxPostsPerActor	Default 20. 0 exports profiles only.
Include replies	includeReplies	Default false.
Include reposts	includeReposts	Default false. The reply filter still applies.
Delay between feed pages	requestDelayMs	Default 150 milliseconds.
Run budget for testing	maxRunSeconds	Optional 35–300 seconds. See field help for deadline behavior.

Input-field help explains ranges and limitations. The form prefills bsky.app, but API calls must supply actors.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Profile and post rows share a dataset. Fields depend on recordType and upstream availability. Missing optional values may be absent rather than zero or an empty string.

Illustrative structure only—not an observed extraction:

{
  "recordType": "post",
  "inputActor": "bsky.app",
  "actorHandle": "bsky.app",
  "uri": "at://example/app.bsky.feed.post/example",
  "url": "https://bsky.app/profile/bsky.app/post/example",
  "text": "Illustrative public post text",
  "isReply": false,
  "isRepost": false
}

Fields	Meaning
recordType, inputActor, actorDid, actorHandle, profileDisplayName, url	Row type, requested account identity and profile/post link
profileDescription, profileAvatar, followersCount, followsCount, postsCount, profileIndexedAt	Profile-only details when available
uri, cid, text, createdAt, indexedAt	Post identity, content and timestamps
replyCount, repostCount, likeCount, quoteCount, bookmarkCount	Available public engagement counts
authorHandle, authorDid	Original post author. May differ from the requested account for reposts
isReply, isRepost, replyParentUri, replyRootUri	Reply/repost flags and available thread references
repostedByHandle, repostedByDid, repostedAt	Repost provenance when returned
embed, labels	Public embed object and labels when returned

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

A start event is charged once per run. Each profile or post saved to the dataset is one result event, so an available account can add a charged profile row even when no posts match.

Rows saved before a later failure remain available and chargeable. Use a small account list and post cap when starting.

See the live Pricing tab for current rates and plan discounts.

Tips for best results

• Start with one named account. Enter its handle or DID rather than a profile URL, and choose a low post cap. API calls must provide actors, even though the form prefills bsky.app.
• Use zero posts for profile reports. Set maxPostsPerActor to zero when you only need profile details. Remember that profile rows count as saved results.
• Choose replies and reposts deliberately. Both are off by default, and enabling reposts does not override the reply filter. Check original authors when including shared material.
• Separate row types before analysis. Use recordType so profile metrics and post engagement are not mixed in one calculation.
• Check status before using a snapshot. Saved rows can remain after a later failure. Review the run outcome before treating the sample as complete.

Limits and caveats

• Recent public feeds only. Public access, upstream availability, deleted posts and filters can reduce the sample. There is no full-history or completeness guarantee, keyword search or private-data access.
• Failures can leave charged rows. Rows saved before a later failure remain available and chargeable. An invalid or unavailable account can fail the run. Inaccessibility alone does not establish why the account is unavailable.
• Deadlines can fail the run. The run budget can stop collection before every account or post is processed. A deadline failure is not automatic resumption or a successful partial run.
• Media and counts depend on Bluesky. Embeds and engagement counts reflect what the source returns. The Actor does not download media files or sort posts by engagement. Optional fields can be absent rather than zero.
• Reposts can have another author. Check the original author and repost fields rather than assuming all returned text belongs to the requested account. Reply references do not include full threads.

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-profile-feed-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "actors": [
    "bsky.app"
  ],
  "maxPostsPerActor": 20,
  "includeReplies": false,
  "includeReposts": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/bluesky-profile-feed-scraper').call({
  "actors": [
    "bsky.app"
  ],
  "maxPostsPerActor": 20,
  "includeReplies": false,
  "includeReposts": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/bluesky-profile-feed-scraper').call(run_input={'actors': ['bsky.app'], 'maxPostsPerActor': 20, 'includeReplies': False, 'includeReposts': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Bluesky Profile Feed 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 Profile Feed 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-profile-feed-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 Profile Feed Scraper by Fetch Cat, or give it the identifier fetch_cat/bluesky-profile-feed-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

Give your assistant the inputs it needs along with a request like one of these:

• “Collect the public profile for bsky.app with Fetch Cat's Bluesky Profile Feed Scraper, without any posts. Show its bio, DID, source link and available follower, following and post counts.”
• “Get up to five recent posts from bsky.app, excluding replies and reposts. Show text, dates and source links, then help me summarize the announcements in the returned sample.”
• “Collect up to ten recent feed posts for the Bluesky handle I provide, including reposts but excluding replies. Show the original author and available repost context so I can distinguish shared posts from the account's own text.”

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.

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

Can I export Bluesky profiles without collecting posts?

Yes. Supply handles or DIDs and set maxPostsPerActor to 0. No Bluesky account credentials are required.

Why are replies or reposts missing?

Both are excluded by default. Enable the relevant input option. Enabling reposts does not override the reply filter or fetch complete conversations.

Why did I get fewer posts than requested?

The limit is a maximum after filtering. Feed exhaustion, unavailable data or the run budget can reduce the sample. Optional fields appear only when returned upstream.

Is this a Bluesky API alternative for search or full history?

It provides an Apify interface for named public profiles and recent account feeds, not keyword search, private data or a complete archive. Use the related Actors for account discovery or follower collection.

Related Actors

• Bluesky Actor Search Scraper — Find public accounts before collecting their profiles and feeds.
• Bluesky Followers Scraper — Collect public follower relationships.
• Threads Profile & Posts Scraper — Collect profiles and posts from another social platform.
• Reddit Scraper — Build complementary public discussion datasets.
• YouTube Channel Videos Scraper — Collect channel video metadata for cross-platform reporting.

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 a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

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