# Bluesky comments API > Markdown version of https://postlake.dev/social-media-comments-api/bluesky . The canonical page for humans. > PostLake is the social media API for AI agents: https://postlake.dev/llms.txt Comments on Bluesky through the same call you use for every other network, with Bluesky's real rules enforced before anything is sent. Reading comments on Bluesky One call returns the replies on a post you published, paged with a cursor, in the same shape as every other network. curl "https://api.postlake.dev/v1/posts/post_…/comments?limit=50" \ -H "Authorization: Bearer $POSTLAKE_API_KEY" Every list also returns problems, naming any network that could not be read. That field is the point: without it an empty list is ambiguous, and "nobody commented" is indistinguishable from "we could not look". An agent acting on the first when the second is true will draw exactly the wrong conclusion. Replying Bluesky allows replying to someone else's comment through the API, so a reply is one more call with the comment id. Bluesky also supports a first comment: a reply posted automatically on your own post the moment it publishes, which is the usual home for links and hashtags you do not want in the caption. Notifications, not polling Bluesky exposes notifications, so GET /v1/notifications merges likes, replies, mentions and follows across networks into one cursor-paged list rather than making you poll each post. Common questions ### Can I read Bluesky comments through an API? Yes, on posts you published. PostLake returns them cursor-paged in the same shape as every other network, alongside a problems field naming anything that could not be read. ### Can I reply to a comment? Yes on Bluesky, with the comment id. The reply goes out as your connected account. ### How do I know a read actually worked? Every list carries problems. If a network could not be read it is named there, so an empty list is never mistaken for silence from your audience. ### Can an agent handle replies? Yes. Over MCP it is read_comments and reply_to_comment, and you can restrict which brands and networks a given agent may act on before you let it run. ## Related - [Post to Bluesky via API](https://postlake.dev/post-to/bluesky.md) - [Scheduling on Bluesky](https://postlake.dev/social-media-scheduling-api/bluesky.md) - [Analytics on Bluesky](https://postlake.dev/social-media-analytics-api/bluesky.md) - [Messaging on Bluesky](https://postlake.dev/social-media-messaging-api/bluesky.md)