aturi.to

You have a web URL (bsky.app, a Leaflet page, a Tangled repo, any Atmosphere client — or an arbitrary page that might declare AT Tags) or an at:// URI, and you want the record behind it plus every client that can open it, each with a ready URL.

You want to know which Atmosphere clients exist and what each can do, with no record in hand: 25+ apps with the record types they render and whether they accept compose-intent links.

You have an atproto handle, DID, or at:// URI and need the canonical identity behind it: the DID, the current handle, the PDS host where the repo lives, and the DID document summary (alsoKnownAs, declared services).

You have 1 to 100 did:plc or did:web identifiers and need their current handles, PDS hosts, and PLC creation times in one call.

You have an account and want its identity timeline: when it was created, every handle it has used, PDS migrations, and key rotations, from the PLC directory audit log.

You have an account and want the shape of its repository: which collections (lexicons) it actually holds, its PDS, when it last wrote, and its Bluesky-layer profile if one exists.

You know which repo and which collection (from describe_repo) and want the records themselves: one page of full record values with their at:// URIs, plus a cursor for the next page.

You have a record address — an at:// URI, or repo + collection + rkey — and want the record JSON.

You have a PDS hostname (from resolve_identity or describe_repo) and want to know about the server itself: its metadata, software version, and a sample of the repos it hosts.

You have a record (at:// URI) or an account (DID/handle) and want what references it across every app, including lexicons you have never heard of: vouches, annotations, mentions, follows.

You have 1-25 account identifiers and want their Bluesky-layer profile cards: display name, bio, follower/post counts.

You have a Bluesky post (at:// URI or a bsky.app-style URL) and want the conversation: the post, its ancestors, and replies as a simplified tree with text, authors, and counts.

You need posts matching a query: full-text search over the Bluesky network, filterable by author, language, and time range.

You need to find accounts by name or topic: full search over Bluesky profiles (handles, display names, bios).

You want an account's recent posts in reverse chronological order, each with its like, repost, reply, and quote counts — so you can summarize what someone has been posting about or find their most-engaged posts (sort the results by likeCount).

You want what is trending on Bluesky at this moment: topics with their post volume, a category, and a few accounts driving each one.

You want the accounts an actor follows: one page of profile cards, with a cursor for more.

You want the accounts that follow an actor: one page of profile cards, with a cursor for more.

You have a Bluesky post and want the accounts that engaged with it: who liked it, who reposted it, or who quoted it (pick one with "kind").

You already have post at:// URIs — from get_backlinks, sample_jetstream, list_records, anywhere — and want them as readable posts with text, author, and engagement counts, up to 25 in one call.

You have an account and want others like it: the "more like this" list Bluesky computes from the graph, which is a fast way to map a community around someone.

You want the starter packs an account has published: curated bundles of accounts and feeds that new people can follow in one action.

You have labeler DIDs and want what those moderation services actually do: the label values each one publishes and who runs it.

You want the network pulse: which lexicons (record types, i.e.

You have an NSID and want its activity profile: creates/updates/deletes and distinct accounts over a window, with a time series showing whether it is growing, steady, or a spike.

You have a word or fragment ("blog", "recipe", "leaflet") and want matching lexicon NSIDs with their activity counts — the way into a corner of the Atmosphere when you do not know its NSIDs yet.

You want to see what activity in a lexicon actually looks like right now: the newest records network-wide in that collection, straight from the live stream sample, with full record values.

You have an NSID and want its published schema: the com.atproto.lexicon.schema record defining the type, found via the _lexicon DNS authority method (with the publisher-handle convention as fallback).

You want custom feeds (algorithmic timelines people publish): "actor" lists the ones an account created, "popular" ranks the network's most-liked and takes an optional query, "suggested" returns Bluesky's editorial picks.

You have feed at:// URIs and want what each feed is: its name, description, creator, and like count, up to 25 at once.

You have a feed generator URI and want the posts it is serving right now, with engagement counts, newest page first.

You want the lists an account has published: curation lists that can be read as a feed, and moderation lists used for muting or blocking.

You have a list URI and want the list itself plus a page of its members as profile cards.

You have a curation list and want what its members are posting, as one combined feed with engagement counts.

You want a live sample of what is happening on the network right now: open Jetstream for a few seconds and return the events seen.

You have a question about how atproto works, how to build on it, or which service to point at: identity, repositories, lexicons, OAuth, feeds, moderation, Jetstream, the relays.

You have a page id from search_atproto_docs and want the whole thing rather than the matching passages: a tutorial, spec, or selected Bluesky GitHub guide.

You want the endpoint or record type for a task and do not know its NSID: "how do I follow someone", "what returns a thread", "where do labels live".

You have an NSID and want its exact definition: every parameter with its type and whether it is required, the request and response schemas, and the named errors it can return.