Social · head-to-head
Bluesky vs Open Collective
Bluesky is the decentralized social network built on the AT Protocol, where posts, follows, and identity live on portable Personal Data Servers instead of one company's database. Its public AppView at public.api.bsky.app exposes keyless, read-only XRPC methods such as app.bsky.actor.getProfile and app.bsky.feed.getAuthorFeed, so any client can pull public profiles and feeds without registering an app. Posting, following, or reading a signed-in user's private data instead requires an authenticated session against a Personal Data Server via an app password or OAuth, not a single global API key.
Open Collective's GraphQL API (v2) queries collectives, expenses, transactions, and members for the platform's transparent nonprofit/open-source funding model, and public collective data is readable with no authentication at all. Its own docs flag the older REST API as still running but no longer developed, pointing new integrations at the GraphQL surface and a companion PDF service (for receipts and invoices) that accepts either a personal token or an OAuth bearer token. A personal access token, not a full OAuth app-review flow, is the documented way to authenticate for private or write access.
| Bluesky | Open Collective | |
|---|---|---|
| Authentication | None | API Key |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
Bluesky needs no API key, while Open Collective requires API Key — pick Bluesky to start without signup.