Social Fanout is the social-publishing API for apps and AI agents. Connect an account once, then one authenticated call ships your post to X, LinkedIn, Instagram, TikTok, YouTube, Bluesky and more — no SDK maze, no OAuth hell, no per-platform rewrites.
Shipping "post to social" sounds like a weekend feature. Then you meet twelve OAuth reviews, twelve token stores, twelve media-upload quirks, and twelve ways to fail in production.
Sign up free, no credit card. Your dashboard key works against the REST API and the local MCP server immediately.
$ export KEY=sf_live_…
One redirect per platform. We store and refresh tokens server-side — your code never touches raw platform credentials.
GET /v1/connect/x → ✓ linked
One POST /v1/publish with one payload shape fans out to every connected target and returns per-platform receipts.
POST /v1/publish → 4/4 ✓
// One key. Every platform. One call. const res = await fetch('https://socialfanout.com/v1/publish', { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ text: 'Shipping something great today.', targets: ['x', 'linkedin', 'bluesky', 'instagram'] }) }); const { results, summary } = await res.json(); // summary → { requested: 4, succeeded: 4, failed: 0 }
POST /v1/publish takes one payload shape
— text, images, or video — the same request whether
you target one network or all twelve. No platform SDK maze, no
per-network rewrites.
Every publish returns a jobId and a
receipt per target — so a failure tells you which network and why.
One redirect to connect. Tokens stored and refreshed server-side — your code never holds raw credentials.
Point Claude or any agent at the MCP server — same key, gateway, and audit log. Zero raw tokens in the agent.
One contract across every network your audience actually uses.
Production runs on Railway with CI-backed deploys and a public health check. Use the hosted API or run your own instance, same code.
Skip the twelve OAuth reviews, token storage, and per-network publish contracts. One key, one call, done.
Give an agent auditable posting over MCP or REST instead of raw platform credentials. Every action logged and reversible at the key.
Onboard a client's accounts in minutes, publish across every available channel, and keep receipts, logs, and limits in one place.
I'd wired the same twelve OAuth flows one too many times. The whole point of Social Fanout is you write the publish once and never think about a platform API again.
The per-platform receipts are the part I'm proudest of. When a post fails you get the exact provider error back — not a shrug. That's the line between a toy and real infrastructure.
We pointed a Claude agent at the MCP server and it just published — to six networks, full audit trail, zero raw tokens. That's the workflow we want every builder to have.
Straight from the team building it — customer stories land here as the beta rolls out.
Every plan includes the REST API and local MCP access. Keys provision automatically and enforce platform-type and monthly publish limits. Platform availability depends on provider approval and account permissions.
Facebook and Instagram count as separate platform types. A publish is one attempted post to one destination platform. Platform availability depends on provider approval, account permissions, app review status, and upstream API health.
No. You connect each account with a standard OAuth redirect. Tokens are stored encrypted and refreshed server-side. Your app and your agents never touch raw platform credentials — they only ever use your Social Fanout API key.
Yes. Nothing posts without an explicit POST /v1/publish
call. Every publish returns a jobId and a per-platform
receipt, and the dashboard logs every attempt with its status and
provider error.
Twelve destination types share one contract: Instagram, X, LinkedIn, TikTok, YouTube, Facebook, Pinterest, Bluesky, Threads, Reddit, Discord, and Email (SMS via Twilio is shipping soon). Each goes live for your account as its provider approval and your permissions allow. Right now TikTok is in app review (posts land on your connected test account until approved) and Pinterest is in limited/trial access (reads work; pin-writes are gated). The dashboard shows live status per connection, so you always know before you publish.
Both, on the same key and the same logs. Call /v1/publish
from your app, or wire the local MCP server into agent clients.
Production is hosted on Railway with CI deploys and a public health
check, and you can run your own instance.
One attempted post to one destination platform. Plans cap your monthly publish attempts and how many platform types you can target. Facebook and Instagram count as separate platform types.
Grab a free key, connect an account, and fan your first post out to every network your audience lives on — in the next two minutes.
New providers, approval milestones, AI-agent examples, and early customer notes. The list for people building on socialfanout.com as the surface expands.