Social listening and trend tracking
Blueskyエンドポイントを使えば、「Social listening and trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Bluesky's public AT Protocol data into structured social data — account search, full public profiles, an account's post feed, followers and follows, a post's full reply thread, and platform-wide trending topics, all as normalized JSON. Credential-free, no auth required.
Search Bluesky accounts and get profiles, posts, follower/following lists, post threads, and trending topics as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
36
サンプル数
11
ライブカタログスナップショット
稼働エンドポイント
11
メソッド
GET
必須パラメータ
21
スキーマ参照
11
{
"platform": "Bluesky",
"endpoint": "bluesky-search-actors",
"method": "GET",
"path": "/bluesky/search-actors",
"auth": "apiKey"
}ユースケース
Search Bluesky accounts and get profiles, posts, follower/following lists, post threads, and trending topics as structured JSON.
Blueskyエンドポイントを使えば、「Social listening and trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Blueskyエンドポイントを使えば、「Creator and account research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Blueskyエンドポイントを使えば、「Conversation and thread analysis」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のBlueskyエンドポイントカタログから取得しています（エンドポイント11件、ドキュメント化されたリクエストパラメータ36個、公開レスポンススキーマ11件）。DocsとPlaygroundが参照しているカタログと同じものです。
Blueskyのエンドポイントは11件、11つのリクエストファミリーに分類されています（Author Feed、Followers、Followsほか8件）。
これらのBlueskyエンドポイントには36個のリクエストパラメータがドキュメント化されており、うち21個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
11件のBlueskyエンドポイントのうち11件が実際のサンプルレスポンスを、11件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Blueskyのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、500、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Blueskyのエンドポイントは11個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/bluesky/author-feed
/bluesky/followers
/bluesky/follows
/bluesky/post-likes
/bluesky/post-quotes
/bluesky/post-reposted-by
エンドポイントカタログ
/bluesky/search-actorsReturns Bluesky accounts matching a query against display name, handle, and profile description.
レスポンスに関する注記
- Each result's `handle` (or `did`) is usable directly as the `actor` parameter to [`/bluesky/profile`](bluesky-profile.md), [`/bluesky/author-feed`](bluesky-author-feed.md), [`/bluesky/followers`](bluesky-followers.md), or [`/bluesky/follows`](bluesky-follows.md).
MCPツール bluesky_search_actors
/bluesky/profileReturns a Bluesky account's public profile: display name, description, avatar/banner images, and follower/follows/posts counts.
レスポンスに関する注記
- An unknown handle/DID returns `404`.
MCPツール bluesky_profile
/bluesky/author-feedReturns a page of a Bluesky account's posts, newest first, including text, engagement counts, and any attached images/link card/quoted post.
レスポンスに関する注記
- Each result's `uri` is usable directly as the `uri` parameter to [`/bluesky/post-thread`](bluesky-post-thread.md). - A post embeds at most one of `images`, `external`, or `quoted_post_uri` (a quote-post-with-media embed sets both `images`/`external` and `quoted_post_uri`).
MCPツール bluesky_author_feed
/bluesky/followersReturns a page of a Bluesky account's followers. `actor` is required and is a handle such as `bsky.app` or a DID. `limit` is 1 to 100 (default 25); pass the returned `cursor` back to continue. Each follower has `did`, `handle`, `display_name`, `description`, `avatar_url` and `created_at`, and `subject` describes the account itself.
MCPツール bluesky_followers
/bluesky/followsReturns a page of the accounts a Bluesky account follows.
MCPツール bluesky_follows
/bluesky/post-threadReturns a Bluesky post along with its nested replies (and, when the post is itself a reply, its parent chain), up to `depth` levels deep.
レスポンスに関する注記
- `uri` must start with `at://`; otherwise `400` is returned before any upstream request is made. - A deleted, blocked, or otherwise inaccessible reply is silently dropped from `replies` rather than surfaced as an empty entry. - A post that no longer exists returns `404`.
MCPツール bluesky_post_thread
/bluesky/trending-topicsReturns Bluesky's current trending topics and suggested feeds, each with a link to its feed. This surface is less stable than the rest of this family -- Bluesky may change its shape without notice.
レスポンスに関する注記
- This surface is sourced from AT Protocol's `app.bsky.unspecced.*` namespace, which is less stable than the rest of this family — Bluesky may change its shape without notice.
MCPツール bluesky_trending_topics
/bluesky/post-likesLists the accounts that liked a Bluesky post, identified by its `at://` post `uri`, which is required. `limit` defaults to 25 and is capped at 100; pass the returned `cursor` back for the next page. Each actor has `did`, `handle`, `display_name`, `description`, `avatar_url` and `created_at`.
MCPツール bluesky_post_likes
/bluesky/post-quotesLists the Bluesky posts that quote a given post, identified by its `at://` post `uri`, which is required. `limit` defaults to 25 and is capped at 100; pass the returned `cursor` back for the next page. Each post has its `text`, `author`, `created_at`, `langs`, like, quote, reply and repost counts, `images` and `external` link card.
MCPツール bluesky_post_quotes
/bluesky/post-reposted-byLists the accounts that reposted a Bluesky post, identified by its `at://` post `uri`, which is required. `limit` defaults to 25 and is capped at 100; pass the returned `cursor` back for the next page. Each actor has `did`, `handle`, `display_name`, `description`, `avatar_url` and `created_at`.
MCPツール bluesky_post_reposted_by
/bluesky/postsReturns public Bluesky posts for 1-25 at:// post URIs. Missing, deleted, or blocked posts are omitted when the public AppView omits them.
MCPツール bluesky_posts
関連API
Social & Creator Platforms
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
Blueskyのスクレイピング方法
Crawlora's Bluesky endpoints return profiles, feeds, follower graphs, threads, and trending topics as normalized JSON with one API key — no Bluesky account or auth token required.
Send a keyword to /bluesky/search-actors, or a handle or DID to /bluesky/profile — bsky.app resolves as readily as its did:plc identifier. A profile returns snake_case counters including followers_count and posts_count.
Pass a handle or DID as actor to /bluesky/author-feed for their posts, or to /bluesky/followers and /bluesky/follows for their social graph.
search-actors, author-feed, followers and follows all take limit and cursor. Pass the cursor from the previous response to continue — there is no page number, and a large account's follower list is only reachable this way.
Pass a post's AT-URI to /bluesky/post-thread for that post and its reply tree, with an optional depth to bound how far down you walk.
/bluesky/trending-topics takes no parameters and returns the platform's current trending topics — around ten at a time, phrased as short headlines rather than hashtags.
On 2026-10-30 /bluesky/followers for bsky.app at limit 25 returned 15 followers but still a cursor, while follows returned 25 and the author feed returned 25 posts with an ISO timestamp cursor. Keep following cursors until none returns.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Bluesky のデータを JSON として取得できます。Bluesky に対応するスキル:
Researches Bluesky profiles, posts, follower/follows graphs, account search, and trending topics via the Crawlora API, returning clean JSON. Use…
npx skills add github.com/Crawlora-org/crawlora-skills --skill bluesky-researchResearches public profiles, posts, trends, and Facebook Marketplace listings across Instagram, TikTok, Threads, Bluesky, X, Pinterest, LinkedIn…
npx skills add github.com/Crawlora-org/crawlora-skills --skill social-media-researchFAQ
Send a keyword to Crawlora's /bluesky/search-actors endpoint and get matching account profiles as structured JSON — no Bluesky account required.
No Bluesky login or auth token is required from the caller — Bluesky's AT Protocol AppView exposes this data with zero auth, and Crawlora only requires your own API key.
Yes — /bluesky/post-thread returns a post and its nested reply tree as structured JSON, and an optional depth parameter bounds how deep it walks so a very long conversation does not return more than you need.
With the cursor, not a page number. /bluesky/followers, /bluesky/follows, /bluesky/author-feed and /bluesky/search-actors each accept limit and cursor and return a cursor for the next page — keep passing it back until none is returned. This matters on large accounts: bsky.app alone reports over 34 million followers, so a cursor loop is the only way through.
Either form works. The actor parameter accepts a handle such as bsky.app or the underlying did:plc identifier, because both resolve through the same AT Protocol AppView. Handles can change while DIDs are stable, so store the DID if you are tracking an account over time.