Guides · Bluesky

Bluesky API and AT Protocol: Choose Search, Records or Streams

Understand Bluesky public reads, AT Protocol identifiers and streaming data. Choose an API or MCP workflow and retain sources that reviewers can resolve.

Use Bluesky’s public read APIs for defined lookups and searches, AT Protocol tooling for repository or streaming requirements, and an MCP workflow when an assistant should help investigate a small question. These options expose different layers of the same ecosystem. Choosing one starts with the records and operational behavior you need.

A journalist following one public conversation does not need to operate a network-wide stream. A developer maintaining a changing index may need much more than keyword results. Treat “Bluesky API” as the beginning of the specification, then name the exact data and update pattern.

Know which service owns the operation

Bluesky’s API hosts guide distinguishes public application reads, authenticated account operations and event streams. Many public reads can go to https://public.api.bsky.app; record writes and account management use the appropriate personal data server with authentication. An endpoint name alone does not tell you that every operation belongs on the public host.

The AT stack guide explains the roles of personal data servers, relays and application views. In practical research terms, a search result is a selected view of data, while consuming a stream is an ongoing collection and maintenance job. The ability to read one does not mean you have implemented the other.

Compare the scope of the job before choosing an interface.
Question you need to answerUseful starting point
Find public posts about a topicA supported keyword search and a reviewable result sample.Inspect source links and follow useful conversations.
Inspect a known public postA direct post lookup.Preserve the returned identifier and surrounding thread context.
Review a feed or listA feed or list lookup matching that object.Keep its identity; a curated list is not the whole community.
Maintain a changing data indexA defined stream or repository architecture.Plan checkpoints, reconciliation and removal handling in your own system.

Preserve identifiers that survive a useful review

The AT URI specification describes references to repository records. It notes that handle-based references are not durable when handles change or are reused, and that an AT URI does not freeze a record’s contents. A reviewer needs to know both which record you meant and what you observed at collection time.

  • Display link: the human-readable post or profile URL used during review.
  • Record identity: the returned AT URI and account identity where available. Prefer the source’s identifier over reconstructing one from a display name.
  • Version context: a content identifier when supplied and needed, plus the capture time. Do not imply that a saved link preserves the original text.
  • Collection method: the search or lookup, fields, sort, page and stopping rule.
  • Conversation context: parent and quoted-post references where relevant to the observation.

Design one small public-topic investigation

Suppose you are checking public discussion of an accessibility release. First define the product, release date and the question: which setup steps need clarification? Search the relevant terms, inspect a few matching posts, and follow replies that explain the difficulty. A feed or starter pack can suggest more accounts to review, but inclusion there is not proof of expertise or a representative sample.

  1. Search for the issue. Use the supported words, hashtags or account filter. Record the exact query and the time you ran it.
  2. Inspect useful records. Open a selected post and its available replies. Check whether it concerns the correct release and whether a follow-up resolved the issue.
  3. Compare independent examples. Separate one conversation with many replies from multiple independent reports. Keep reposts and quotes tied to the source they discuss.
  4. Write a bounded conclusion. Describe the observed setup questions and source links. Propose a documentation correction or usability test rather than estimating the opinion of all users.

Superlurk reads the public Bluesky network directly for its accepted Bluesky searches. These include posts, accounts, threads, feeds, list members and starter-pack accounts. The catalog is a collection of defined reads, not a customer streaming API. The assistant should show the proposed searches and credit quote before running the investigation.

Investigate public Bluesky discussion of a product’s accessibility release. Suggest a small query plan and show the quote first. After approval, inspect useful posts and replies. Return the question, source URL, returned record identifier where available, collection time, any correction in the thread and a proposed documentation test.
Illustrative workflow, not a measured search result

Choose streaming only when the question requires it

A stream-based application needs its own decisions about duplicates, reconnects, missing intervals and records that change or disappear. Define what the index promises and how it recovers before treating a stream as a complete archive. For a short evidence review, a small search and lookup plan may answer the actual question with much less operational work.

For the researcher-facing process, read the Bluesky search guide. Use the feeds, lists and starter-pack guide to distinguish curated objects. The API vs MCP comparison helps decide who should control the next request.

Frequently asked questions

Can Bluesky public data be read without signing in?

Many public Bluesky reads can use the public API without authentication. Writes, account management and private data have different requirements; check the endpoint and correct host.

Is an AT URI the same as a normal post link?

No. An AT URI identifies repository data. A bsky.app URL is an application link. Keep both where available so software and human reviewers have useful references.

Does Superlurk offer a full Bluesky firehose?

Superlurk offers defined public Bluesky searches and lookups. Its MCP interface is not a firehose subscription or a guarantee of a complete network archive.

Sources

  1. Bluesky: API hosts and authentication
  2. AT Protocol: the AT stack
  3. AT Protocol: AT URI scheme

How this guide was written. Reviewed on 11 November 2026 against the primary references below and Superlurk’s accepted search catalog and public methodology. Workflows, example queries and sample records are editorial illustrations, not customer results or measured performance. Native API access rules and product availability can change.

The Superlurk TeamSocial research

We build Superlurk for public-data research across 25 supported social networks, with the price shown before every search. We write practical guides to search methods, source verification and AI-assisted research.

Start lurking for free.

Every network, no card needed. See the price first, and pay nothing if a search fails.