Bluesky AT Protocol alternative (2026)
Bluesky's AppView is already public — getProfile, getAuthorFeed, and getPostThread do not need OAuth. Captapi is useful when you want those records as the same camelCase JSON as our other platforms, with isRepost marked and embeds normalized, without speaking AT Protocol.
Is Captapi a good Bluesky AT Protocol alternative?
Use Captapi when the rest of the job is already on our key, or when you want isRepost / repostedBy / normalized embed types (external | images | video | quote) instead of lexicon NSIDs. Call bsky.social / the public AppView directly when Bluesky is your only source, when you need a custom AppView client, or when you write (create a post, like, follow) with an app password. Captapi does not write.
Captapi vs Bluesky AT Protocol
| Captapi | Bluesky AT Protocol | |
|---|---|---|
| Public read auth | Captapi Bearer key — not because Bluesky requires it, because our envelope does | None for AppView getProfile / getAuthorFeed / getPostThread |
| Response shape | Same camelCase profile/post keys as other Captapi platforms | AT Protocol lexicon (app.bsky.feed.post, embed NSIDs) |
| Reposts on the author feed | isRepost + repostedBy + repostedAt; includeReposts=false drops them | You detect reason.repost yourself |
| Embeds | type external | images | video | quote — quote includes uri/url/text/author | Lexicon union (app.bsky.embed.*) |
| Write (post / like / follow) | No | App password or OAuth on your PDS |
Comparison of public, documented behaviour as of October 2026. Official APIs change — verify on docs.bsky.app.
When to use which
Use Captapi when
Use Captapi when the rest of the job is already on our key, or when you want isRepost / repostedBy / normalized embed types (external | images | video | quote) instead of lexicon NSIDs.
Use Bluesky AT Protocol when
Call bsky.social / the public AppView directly when Bluesky is your only source, when you need a custom AppView client, or when you write (create a post, like, follow) with an app password. Captapi does not write.
Matching Captapi endpoints
Why developers pick Captapi
- Same profile/post keys as Instagram and TikTok — no lexicon NSIDs in your app
- isRepost / repostedBy so analytics do not credit someone else's likes
- Nested replies[] on post-details (depth 0–6)
- Docs say the quiet part: Bluesky-only jobs can skip us
Worked examples
Frequently asked questions
Is Captapi a Bluesky API alternative?+
Only as a normalized JSON client. Bluesky's AppView is public. If Bluesky is your only platform, call it directly. If you already use Captapi, the Bluesky endpoints match the rest of the catalog.
Do I need a Bluesky app password?+
Not for Captapi reads. App passwords are for write actions on your PDS. We do not post, like, or follow.
Why is the first user-posts row a different author?+
It is a repost. isRepost is true and author{} is the original poster; repostedBy is the profile you queried. Pass includeReposts=false to drop them.
Other official API alternatives
One REST key across 33 platforms — not just this one.
Try Captapi free
Get your API key and 100 free credits in 60 seconds. No credit card.