Bluesky posting API: how to compare providers for auth, limits, alt text, and scheduling
A Bluesky posting API earns its place only when it manages the platform-specific details that a generic posting api often ignores. This guide uses one shared checklist for Zernio, Post for Me, Outstand, and Ayrshare, covering credentials, length, accessibility, feed language, timing, and throttling, so you can judge each option against your cross-posting needs.
What a Bluesky posting API must handle
Bluesky runs on the AT Protocol, and that open protocol shapes what a bluesky api needs to do. A generic posting api that only sends text will miss the platform-specific work: credentials based on an app password rather than OAuth, the 300-character cap, alt text for accessibility, language tags so the AT Protocol can surface a post in the right feeds, and rate limits that can interrupt scheduled publishing. Use this page to score each provider against the same checklist before you write integration code.
Field map and input contract for a Bluesky post
Start with the field map in the Create a Bluesky post with the shared posts contract example. Text must be checked against the 300-character cap before sending. Each image attachment needs alt text, not a single caption-level description, because Bluesky users expect per-attachment accessibility text. Language tags should use BCP-47 codes so the post is surfaced appropriately. Scheduling should be explicit: either post now or provide a scheduled time, and the provider should make clear what happens if the scheduled time is in the past or the account disconnects before the slot. Authentication should use app-password auth, with the credential stored securely and never shipped to a browser.
Zernio: broad coverage with per-connected-account billing
Zernio, formerly Late, supports Bluesky as part of a wide platform list. That breadth is the main reason to consider it if you also need niche platforms such as Reddit or Telegram alongside Bluesky. On its official pricing page checked on 2026-11-15, Zernio uses per-connected-account usage billing with two accounts free, every feature included, no fixed plans and no seats; enterprise pricing is custom above 2,000 accounts. The page gives a default 10-account example of $48 per month, but dynamic tier rates were not reliably extracted, so do not treat a single per-1,000-post figure as fixed. Strengths are wide coverage, AI agent integrations such as MCP and ChatGPT, and a free allowance. Weaknesses are that cost scales with connected accounts and that the rename from Late can cause brand confusion. Confirm your exact account count and tier rate on the current pricing page before budgeting.
Post for Me: unlimited accounts and included analytics
Post for Me supports Bluesky with a developer-tool framing: pay per post, unlimited accounts, unlimited team members, and analytics included. On its official pricing page checked on 2026-11-15, the displayed entry price is $10 per month for up to 1,000 successful posts, with unlimited social accounts, API keys, and team members. It includes feeds, post analytics, managed developer credentials, and bring-your-own-key options. Higher tiers are dynamic and were not reliably extracted, so do not invent a larger-pack unit price. Strengths are unlimited social accounts and team members, analytics and feed reading included, and a bring-your-own-credentials option. Confirm whether bring-your-own-credentials changes how app-password auth is stored and revoked, and recheck current pricing before committing.
Outstand: usage-based pricing, MCP, and BYOK for some networks
Outstand supports Bluesky on a usage-based model. On its official facts page checked on 2026-11-15, pay-as-you-go is $19 per month including 3,000 posts, then $0.007 per post for the next 7,000 and $0.005 per post beyond 10,000; Business is $129 per month including 50,000 posts then $0.005 per post. Connected accounts are unlimited. Managed keys cover 8 networks, while X, Google Business, Vimeo, and Reddit require bring-your-own-key. MCP is live with 30 tools. Strengths are transparent usage-based pricing, unlimited accounts, and live MCP support. Weaknesses are no free tier in the verified facts, cost that depends on volume tier, and bring-your-own-key requirements for some networks. Use the tier math for your expected volume rather than a single per-1,000-post figure.
Quick comparison and how to pick one
Use the comparison table below as a scoring sheet, not as a ranking claim. Fill in the Bluesky-specific bits column for your shortlist by testing app-password auth, alt text, language tags, and scheduling with a real account. A provider that looks cheaper per 1,000 posts can become more expensive once analytics add-ons, account-based billing, or profile limits are included. Conversely, a higher monthly plan may be justified if webhooks, analytics depth, or profile capacity remove work from your team. Rival figures below reflect official provider pages checked on 2026-11-15.
Worked example: scoring a provider for cross-posting
Work through a concrete evaluation before coding. First, connect a test Bluesky account using app-password auth and confirm you can disconnect and reconnect without losing scheduled items. Second, submit a post at exactly 300 characters and one that exceeds the cap, and record whether the provider rejects, truncates, or accepts it. Third, post an image with and without alt text and check how the alt text is stored and returned. Fourth, send a post with a BCP-47 language tag and verify the tag is preserved. Fifth, schedule a post, then cancel or reschedule it, and confirm the state change is visible. Score each provider pass, fail, or not supported, then compare cost per 1,000 posts only among providers that pass the functional checks.
Failure matrix: auth, character limit, alt text, language tags, scheduling
The most common failures are predictable. Using OAuth where app-password auth is required will fail at connection time. Exceeding the 300-character cap can cause rejection or silent truncation. Missing alt text produces a post that publishes but fails accessibility expectations. A wrong language tag can reduce correct feed surfacing. Scheduling failures often come from unclear time zones, past timestamps, or accounts disconnected after scheduling. Rate limits should be handled with backoff and a visible failed state rather than blind retries, because repeated retries can worsen throttling and duplicate posts.
| Service | Current pricing basis (official pages, 2026-11-15) | Free tier / trial | Accounts | Bluesky-specific bits |
|---|---|---|---|---|
| Post for Me | $10/month up to 1,000 successful posts | Not stated in verified facts | Unlimited | App password, alt text |
| Outstand | $19/month includes 3,000 posts; then $0.007, then $0.005 | Not stated in verified facts | Unlimited | App password |
| Zernio | Per connected account; 10-account example $48/month; dynamic tiers not extracted | 2 accounts free | Per connected account | App password |
| Ayrshare | Premium $149/1 profile; Launch $299/up to 10; Business $599/30 | Launch 28-day trial | 1 / up to 10 / 30 by tier | App password, webhooks |
Rival figures from official provider pages checked 2026-11-15: Zernio per-connected-account billing, 2 accounts free, no fixed plans, dynamic tiers not extracted; Post for Me $10/month up to 1,000 successful posts, unlimited accounts; Outstand $19/month includes 3,000 posts then $0.007/$0.005, unlimited accounts; Ayrshare Premium $149/1 profile, Launch $299/up to 10, Business $599/30. Publisher row from source table excluded per neutrality policy. Confirm current pricing before committing.
| Failure | Symptom | Check before shipping |
|---|---|---|
| OAuth used instead of app-password auth | Connection fails or credential cannot be stored | Confirm the provider accepts an app password and supports disconnect/reconnect |
| Text exceeds 300-character cap | Rejection or silent truncation | Test at-cap and over-cap posts; require explicit rejection, not truncation |
| Missing alt text | Image publishes without accessibility text | Require alt text per attachment and verify it is returned after posting |
| Wrong language tag | Post surfaced in wrong feeds | Use BCP-47 codes and verify the tag is preserved |
| Scheduling with past time or disconnected account | Post never publishes or publishes unexpectedly | Test schedule, cancel, and reschedule; check time zone handling |
| Rate limits hit | Throttled or duplicate posts on retry | Implement backoff, idempotent retry logic, and a visible failed state |
General integration guidance derived from the field map; provider-specific error codes and status behavior were not supplied and must be verified per provider.
Frequently asked questions
What should I check first when comparing a Bluesky posting API?
Check app-password auth, the 300-character cap, alt text per attachment, language tags, scheduling, account limits, rate limits, and cost per 1,000 posts. A provider that misses alt text or language tags may still post, but the result will be less accessible and less reliably surfaced in the right feeds.
Why does Bluesky use app-password auth instead of OAuth?
Use app-password auth for Bluesky instead of assuming a standard OAuth flow. Store the app password securely, never expose it in client-side code, and test connection and disconnection before scheduling production posts.
What happens if a post exceeds the 300-character cap?
Validate length before sending, shorten or split the copy, and confirm whether the provider counts characters the same way you do. Do not rely on a provider silently truncating text, because that can change meaning and break links or mentions.
How do I compare pricing fairly across providers?
Compare cost per 1,000 posts, free tier, account limits, Bluesky-specific features, and any separate charges for analytics or add-ons. Rival figures in this comparison use official provider pages checked on 2026-11-15; confirm the current plan page before committing, because dynamic tiers can change.
curl -X POST "{{API_BASE_URL}}/v1/posts/" \
-H "x-access-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "A short example update.",
"platforms": [
{ "platform": "bluesky", "accountId": "{{ACCOUNT_ID_PLACEHOLDER}}" }
],
"mediaItems": [
{ "type": "image", "url": "{{IMAGE_URL_PLACEHOLDER}}", "altText": "An illustrative image." }
],
"publishNow": true
}'