Social Fanout is the social-publishing API for apps and AI agents. One authenticated call posts to X, LinkedIn, Instagram, TikTok, YouTube, Bluesky, and more — your code and your agents (Claude, coding agents) ship everywhere through a single key.
# One key. Every platform. One call. curl 'https://socialfanout.com/v1/publish' \ -H "Authorization: Bearer $KEY" \ -d '{ "text": "Shipping day 🚀", "targets": ["x","linkedin","bluesky"] }' # → one job, per-platform results
Ship posting features without spending weeks on OAuth reviews, token storage, upload flows, and provider-specific publish contracts.
Give agents one safe MCP or REST gateway for auditable posting instead of handing them raw platform credentials.
Connect accounts once, publish across available channels, and keep receipts, logs, and upgrade paths in one place.
POST to /v1/publish with one payload shape. No platform SDK maze, no auth headaches, no per-network guesswork.
Connect accounts with a single redirect. We store tokens server-side, refresh where supported, and surface provider errors.
Instagram, TikTok, X, LinkedIn, Facebook, YouTube, Pinterest, Bluesky, Threads, Reddit, Discord, and Email share one publishing surface when the connection is configured and approved. SMS (Twilio) is implemented and shipping soon.
Accepted publishes return a jobId, status, and provider receipt. Dashboard logs expose failures; outbound customer webhooks are still on the roadmap.
Use the REST API directly or connect the MCP server so agent clients can publish through the same safe gateway and logs.
Production runs on Railway with CI-backed deploys and a public health check. Use the hosted service or run your own instance.
// 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 }
Use the free dashboard key to test providers, connect accounts for setup, and prove the publish flow in your product or agent. Platform slots are reserved only when you publish.
Starter covers small automations, Builder is the broader-destination self-serve plan, and Pro raises volume for apps and teams.
Call `/v1/publish` directly from your app or wire the MCP server into agent clients so publishing goes through the same key and logs.
Buffer, Later, Hootsuite, and Sprout are calendar-first. socialfanout.com is API-first for people embedding social publishing inside their own app, workflow, or agent.
Zapier, Make, and n8n connect everything. socialfanout.com specializes in social OAuth, publish uploads, provider receipts, and the messy parts after auth succeeds.
Direct platform APIs mean separate reviews, tokens, media flows, rate limits, and errors. socialfanout.com gives builders one REST and MCP contract.
Every plan includes REST API and local MCP stdio access. Payment and API-key provisioning are automatic; persisted API keys enforce platform-type and monthly publish-attempt limits. Platform availability still 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.
New providers, approval milestones, AI-agent examples, and early customer notes. This is the list for people who want to keep building with socialfanout.com as the launch surface expands.