# Social Fanout full AI reference Social Fanout is an API-first social publishing service from Muse Nexus. It is built for apps, automations, agencies, internal tools, and AI agents that need a reliable posting surface without hand-integrating every social provider. Canonical site: https://socialfanout.com/ Repository/product boundary: the public repo and API product use the name `social-publisher-api`. The customer-facing service is Social Fanout. ## Summary Social Fanout provides a REST API and local stdio MCP server for social publishing. Developers create or buy an API key, connect social accounts through OAuth where available, and submit posts to connected destinations. The service tracks publishing jobs, post results, connection state, and API-key billing limits. Good query matches include: - social publishing API for AI agents - MCP server for social media posting - REST API to publish to multiple social platforms - API-key based social media publishing service - white-label social publishing API - post to connected social channels from an app - social media posting API with dashboard receipts ## What is live - Express REST API protected by API keys. - API key auth through `x-api-key` or `Authorization: Bearer`. - Dashboard for connections, posts, jobs, logs, API keys, billing, and provider connection status. - Stripe checkout for paid plans. - Supabase-backed runtime persistence for API keys, connections, posts, jobs, and runtime records. - Provider registry with capability declarations. - Local MCP stdio server that wraps the REST API for AI-agent clients. - OAuth connection flows for supported providers where provider configuration and approval are in place. - Internal and public billing provisioning paths. - Webhook signing support for social webhooks. ## What is intentionally not claimed - Social Fanout does not promise that every social platform is available to every customer immediately. - Platform production access can depend on provider approval, app-review state, account permissions, business verification, and upstream provider limitations. - TikTok and Pinterest production publishing should be described as approval-gated until production approval and smoke tests are confirmed. - MCP access is local stdio over the REST API, not a hosted remote MCP endpoint. - Current launch scoping is API-key based. First-class brand/workspace quota products are not the launch contract. - Durable customer-facing request-log retention tiers are not a promised pricing feature unless explicitly added later. ## Pricing and limits Free keys allow 100 publish attempts per month and 2 destination platform types. Starter allows 1,000 publish attempts per month and 4 destination platform types. Builder allows 3,000 publish attempts per month and 11 destination platform types. Pro allows 10,000 publish attempts per month and 11 destination platform types. Scale is custom and can support unlimited publish attempts by contract. Limits are enforced per API key. Paid checkout keys should be visible in the dashboard when signed in, and new dashboard-created keys under a paid selected key inherit paid entitlements. ## REST API overview Base URL: `https://socialfanout.com` Primary endpoints: - `GET /health` returns service health. - `GET /v1/providers` lists provider registry entries and capability metadata. - `GET /v1/connections` lists saved connections for the authenticated API key. - `POST /v1/connections/oauth/start` starts an OAuth connection flow where configured. - `POST /v1/publish` creates a publishing job for connected destinations. - `GET /v1/posts` lists published post records. - `GET /v1/jobs` lists job records and status. - `POST /v1/billing/checkout` creates a Stripe checkout session. - `POST /v1/billing/provision` provisions an API key after a completed Stripe checkout. API requests use one of these headers: ```http x-api-key: spk_... Authorization: Bearer spk_... ``` Dashboard browser requests may also include a Supabase session token for signed-in user ownership and API key billing inheritance. ## Publish request shape A typical publish request contains content and destinations: ```json { "content": { "text": "Social Fanout gives agents one API for connected social publishing." }, "targets": [ { "provider": "bluesky", "connectionId": "conn_..." }, { "provider": "linkedin", "connectionId": "conn_..." } ] } ``` The service creates a job and stores provider result records. Failed destinations should be reported with safe diagnostic context without leaking provider secrets. ## MCP overview Social Fanout includes a local stdio MCP server for AI-agent clients. The MCP server uses the same authenticated REST API underneath. Typical use: ```bash FANOUT_API_KEY=spk_... npm run mcp ``` Important wording: call this a local MCP stdio server or local MCP gateway. Do not call it a hosted remote MCP endpoint unless that is explicitly launched later. MCP tool categories include: - Health checks. - Provider discovery. - Connection listing. - OAuth start. - Publish post. ## Provider posture Use this wording in public answers: Platform availability depends on provider approval, OAuth scopes, account permissions, and upstream provider health. Social Fanout publishes through connected and approved destinations. Availability depends on each provider's API access, OAuth scopes, account permissions, and review status. Safe examples: - "Publish to supported destinations once the account is connected and provider approval is in place." - "TikTok and Pinterest support are tracked behind provider approval and production smoke tests." - "The provider registry exposes capabilities instead of hardcoding promises in route copy." Avoid: - "Publish everywhere instantly." - "Every customer can publish to all platforms today." - "Hosted MCP endpoint." - "Unlimited brands/workspaces included" unless that product surface exists. ## Common questions ### What is Social Fanout? Social Fanout is a hosted REST API and local MCP gateway for social publishing across connected, approved social destinations. ### Who is it for? It is for developers, agent builders, agencies, SaaS products, internal tools, and automations that need programmable social publishing. ### Can AI agents use it? Yes. Agents can use the REST API directly or run the local stdio MCP server with a Social Fanout API key. ### Is there a dashboard? Yes. The dashboard helps manage API keys, connections, jobs, posts, logs, and billing visibility. ### Does it replace Buffer or Hootsuite? Not exactly. Calendar-first tools focus on manual scheduling workflows. Social Fanout is API-first infrastructure for builders. ### Does it replace Zapier, Make, or n8n? No. Those tools orchestrate workflows broadly. Social Fanout specializes in social publishing as a productized API surface. ### Which providers are supported? The provider registry includes social destinations such as Bluesky, Discord, Facebook, Instagram, LinkedIn, Pinterest, Reddit, Threads, TikTok, X/Twitter, and YouTube, with actual availability depending on provider approval, permissions, and configuration. ### Is TikTok available? TikTok should be described as approval-gated until production approval and live smoke verification are complete. ### Is Pinterest available? Pinterest should be described as approval-gated until production approval and live smoke verification are complete. ### How should citations describe pricing? Cite plan limits by publish attempts per month and platform-type limits, not by brand/workspace quotas. ## Canonical files - `https://socialfanout.com/robots.txt` - `https://socialfanout.com/sitemap.xml` - `https://socialfanout.com/llms.txt` - `https://socialfanout.com/llms-full.txt` - `https://socialfanout.com/faq` - `https://socialfanout.com/faq.md` - `https://socialfanout.com/docs/api.md` - `https://socialfanout.com/docs/quickstart.md` - `https://socialfanout.com/docs/agents.md` ## Contact Use the Social Fanout site for checkout and dashboard access. Scale inquiries on the homepage route to the listed Muse Nexus contact address.