Decision guide · reviewed 2026-07-30
What can Magnetiq safely do on Bluesky?
AT Protocol exposes feed posts, replies, and chat APIs; Magnetiq sells its text rail and can model a DM close, while live inbox behavior remains provider-dependent.
Good fit
Expertise-led B2B teams already using Bluesky and willing to review early work.
Choose something else when
Not a fit for policy evasion, guaranteed reach, unsupported media, or mass cold outreach.
The workflow
Ground a Bluesky-shaped draft → review → publish through the connected provider rail → reconcile completion → triage supported responses → use a dm close.
A workflow-shaped demonstration
A sub-300-character opinion receives a reply; only after explicit interest does the demonstration show an existing-thread DM handoff.
Current capability matrix
| Layer | Current truth |
|---|---|
| Official API | AT Protocol exposes feed posts, replies, and chat APIs; Magnetiq sells its text rail and can model a DM close, while live inbox behavior remains provider-dependent. |
| Magnetiq publishing | Sellable text rail; review-first before account-specific Autopilot eligibility. |
| Replies | Supported in the product; availability still depends on provider and account permission. |
| Conversation close | DM close supported; production funnel: dm_close. |
| Recovery | Reconnect, edit, retry, wait, billing, or support is shown from the typed failure; completion is never inferred from queue acceptance. |
Official source: Bluesky API documentation, reviewed 2026-07-30.
Boundary
Official API capability, Magnetiq product policy, provider implementation, and live account permission are separate gates. An empty inbox is unknown until a connected account is verified.
Test the relevant path
The sandbox is simulated and publishes nothing.