atproto.at

Taproot exposes read-only AT Protocol data, PDS-agnostic (works for any PDS, relay, or labeler, not only Bluesky). Start with `resolve` for any at:// URI, handle, or DID. Use `get_profile`/`get_record`/`list_records` when you already know the shape, and `search_accounts` to turn a name into candidate DIDs. WORKFLOWS: - Who liked/reposted/replied to/quoted/mentioned/follows X: call `get_backlinks` (counts per category, each carrying a `source`), then `list_backlink_records` with that `source` for the author DIDs and record URIs, then `get_record` on a URI to read what a reply/quote/mention actually says. For a whole conversation, use `get_thread` (ancestors + direct replies). - Never trust a handle from search results or user input before acting on it: `verify_handle` checks the handle's DNS/well-known binding to the DID (anti-spoof). - Moderation labels: `list_labelers` to discover a labeler, then `query_labels` with it (labels key on DIDs; a handle target is resolved for you). - `count_records` may return exact:false with a cursor; call it again with that cursor and ADD the counts. MORE TOOLS: `get_account_history` (handle/PDS/key changes over time, did:plc). `search_lexicons`/`resolve_lexicon` (registry of published lexicons; `search_lexicons` filters by schema kind with `type`, e.g. type='space' for permissioned spaces, and always reports a `typeCounts` breakdown of the matches (plus `otherTypes` for what a type filter excluded) — an NSID does not imply its type). `list_repos_by_collection` (which accounts publish a lexicon, relay-served). `get_did_document` (raw identity doc). `get_app_link` (shareable web/PDS links). `describe_pds`/`get_repo_status` (PDS info, account takedown/active status). `get_latest_commit` (repo head CID/rev). `list_repos` (accounts hosted on a PDS). `get_pds_directory_info`/`get_relay_directory_info` (cached health cards). `list_blobs`/`get_blob_info` (an account's media blobs, and a blob's getBlob URL, content-type, and size). COMPOSE LINKS: to hand the user a prefilled record-composer link, build an at.new URL — https://at.new/?record=<percent-encoded record JSON> for small records, https://at.new/#record=b64:<base64url of the UTF-8 JSON, padding stripped> for anything bigger, or https://at.new/#record=dfl:<base64url of raw-deflate-compressed JSON> to keep large payloads compact (caps: 100 KB encoded, 1 MB decoded). Include "$type" in the record (it selects the collection). The user always reviews and presses Create themselves; nothing auto-posts. Template variables inside string values make the link reusable: {{$now}} (UTC instant), {{$did}}/{{$handle}} (whoever opens it), {{$lang}} (opener's language) resolve at create time. Any OTHER placeholder without a $ — any name you invent, e.g. {{title}} or {{message}} — becomes a text field the opener fills in before creating. Full guide: /new/api on the human host. CONVENTIONS: every list tool returns a `cursor` when more pages exist. Error responses carry a machine-readable `hint`. On a rate-limit error (429), wait retryAfterSec before retrying (heavy tools cost more budget). Add `include:['profile']` on resolve/get_profile/get_record for the repo owner's display name, bio, and avatar URL ('schema' applies to record/collection targets; 'backlinks' means followers when the target is an account). at:// URIs are also readable as MCP resources (resources/templates/list, resources/read), and prompts/list has ready-made recipes (who_engaged, account_audit, pds_health).