For AI agents & vibe coders

Don't let social media APIs
kill your vibe.

You're shipping with Claude, OpenClaw, Hermes. Give your agent one safe skill to publish everywhere — over MCP or a single REST call. No raw tokens, no OAuth babysitting, full audit log.

Get your free API key → Read the MCP docs
Free tier MCP + REST No raw tokens Self-hostable
your-agent · social-fanout (mcp)
agent> publish "shipped v2 🚀" to x, bluesky, linkedin
→ social-fanout · fanning out…
3 published · 0 raw tokens touched · logged
Plugs into the agent you already run
Claude Codex Cursor VS Code OpenClaw ☤Hermes Any MCP client
MCP-native — or a plain POST from any agent that can make an HTTPS call.
One call out → 12 destination types
Instagram X / Twitter LinkedIn YouTube Facebook Bluesky Threads Reddit Discord Email TikTok · in review Pinterest · limited
Pass a targets array — up to 20 in one call — and get a per-target result back. SMS is coming next; here's what's live today.
The agent problem
Your agent shouldn't be holding your X password.

Autonomous agents act on their own. Handing one your raw platform tokens is how a stray loop nukes your accounts at 3am. Social Fanout is the gateway in between.

🔑

No raw credentials

Your agent gets one Social Fanout key. Platform tokens are stored and refreshed server-side — the agent never sees them, so a leaked prompt can't leak your accounts.

🧾

Every action logged & reversible

Each publish returns a jobId and a per-network receipt, and every attempt is logged. Revoke the key and the agent's reach is gone instantly.

🚦

Scoped & rate-limited

Per-key platform and monthly publish limits mean a runaway agent hits a wall, not your reputation. You set the blast radius.

Here's the handoff on real screens: the agent kicks off OAuth, the human approves once on the provider's own page, and the token lives with Social Fanout — never in the agent.

Threads — approve once on Threads' own consent screen.
Pinterest — granular scopes, on Pinterest's own screen.
Wire it in
One skill. Add it to your agent in minutes.

Point your agent at the MCP server, or just have it call the REST endpoint. Same key, same audit log either way.

mcp setup 
# point the local MCP server at your key, then run it
FANOUT_API_BASE_URL=https://socialfanout.com \
FANOUT_API_KEY=spk_live_… \
  npm run mcp
# → your agent gets fanout_publish_post + health,
#   providers, connections & start_oauth. No raw tokens.
Building an agent product?
Ship publishing as a feature of your own agent.

Embed Social Fanout inside your app or agent and offer it to your own users — open by default, no sales call, no closed waitlist. Self-host it on your infra or run on ours, under one license.

Talk about embedding

Give your agent a voice —
not your passwords.

Grab a free key, point your agent at the MCP server, and let it publish to every network your audience lives on — safely.

Get your free API key → Read the docs