Answers for builders shipping social publishing.

socialfanout.com is a hosted REST API and local MCP gateway for social publishing across connected, approved social destinations.

socialfanout.com is for developers, AI-agent builders, agencies, SaaS teams, internal tools, and automations that need programmable social publishing.

Yes. Agents can call the REST API directly or run the local stdio MCP server. A custom GPT can import the hosted Social Fanout Action schema where ChatGPT Actions are available.

Yes, where GPT Actions are available. Import the hosted Social Fanout Action schema into a custom GPT and configure a customer-owned Social Fanout key as Bearer authentication. The Action calls the REST API; it is not a native ChatGPT app or hosted remote MCP server. ChatGPT plan, model, workspace, and domain restrictions still apply. Keep the GPT private or restrict it to people authorized to publish through that key because it is a shared server-to-server credential, not per-user OAuth. Rotate or revoke the key if exposure is suspected.

No. The launch MCP surface is a local stdio server over the hosted REST API. Describe it as local MCP stdio access or a local MCP gateway.

The API accepts post content and destination targets, then creates publishing jobs for connected destinations. Exact media and destination capabilities depend on the provider.

The provider registry includes social destinations such as Bluesky, Discord, Facebook, Instagram, LinkedIn, Pinterest, Reddit, Threads, TikTok, X/Twitter, and YouTube. Actual production availability depends on provider approval, account permissions, OAuth scopes, and configuration.

TikTok is approved and live for production publishing. Standard customer publishing works; per-account availability still depends on the connected account's permissions and OAuth scopes.

Facebook Page publishing is approved. Meta has approved and Published the dedicated Facebook Comments and Facebook Messenger apps. Both are available to eligible Page admins after separate per-Page authorization; separate production canaries on September 7 verified each grant, webhook subscription, inbound receive, explicit reply receipt, and matching native result. Comments replies require an explicit request; Social Fanout does not auto-reply, and the dashboard requires a human click. Messenger supports only explicit text replies in customer-initiated conversations inside the standard 24-hour window; it does not offer cold outreach, automation, media replies, or Human Agent. Instagram image/Reel publishing is approved for eligible Professional accounts through Business Login for Instagram. Threads text/image publishing is approved and live for eligible connected accounts. Instagram Comments and Instagram Messages are available for eligible Professional accounts after separate authorization for each. Comments supports explicit replies, hide/unhide, and deletion of app-created replies. Messages supports customer-initiated, text-only replies inside 24 hours; automatic replies and media replies are not offered.

Pinterest has Standard API access. Connecting an account and selecting a public Board are verified. Publishing remains limited while final publishing verification is completed. Social Fanout never creates or edits Boards. Connecting requires boards:read, boards:write, pins:read, and pins:write permissions. Pins publish immediately; scheduling is not available.

LinkedIn member publishing is available for eligible connected profiles, with periodic reconnect when LinkedIn does not issue refresh access. LinkedIn Page publishing works for Pages administered by the connected member under Development Tier, and refreshable Page connections renew on publish; Standard Tier review is pending for unrestricted customer Page access. LinkedIn uses the dashboard, REST API, or local MCP; the current ChatGPT Action excludes it.

API requests use an API key through x-api-key or Authorization: Bearer. Keys are stored hashed at rest and carry their own plan limits.

Free is $0. The first signed-in Free key gets one seven-day evaluation across every currently available destination, capped at 300 publishes for the whole window. Then the same key remains Free with 2 platform types and 100 publish attempts per month; no card and no automatic charge. Builder is $19/month for 3,000 attempts; the current RIDEORDIE founder discount makes it $9.99/month only while that subscription remains active. Pro is $49/month for 10,000 attempts. Builder and Pro cover all currently available destination platform types. Scale is custom. Starter remains supported only for existing subscriptions. These plan-wide counters still apply to X. X additionally includes 100 text-only posts per API key per UTC month. X posts containing links use prepaid Link Packs: 40 linked posts for $10. Failed provider attempts do not consume the X allowance or a Link Pack credit.

Connecting a provider does not consume a destination platform type. The first publish to a destination type reserves that type for the current UTC month; Facebook and Instagram count separately even when connected through Meta.

Current launch limits are API-key scoped. First-class brand or workspace quotas are not the launch contract.

Yes. Checkout upgrades the exact customer-owned Free key selected before payment. The signed Stripe webhook and return page use the same idempotent fulfillment path, so a browser close or replay cannot mint another key.

When the dashboard has a selected paid key, newly created dashboard keys inherit that paid billing metadata. Otherwise dashboard-created keys start as Free keys.

socialfanout.com stores connection records needed to operate connected accounts. Secrets and API keys are treated as sensitive server-side values.

Those products are calendar-first social media tools. socialfanout.com is API-first infrastructure for builders who need programmable publishing.

Automation tools orchestrate many kinds of workflows. socialfanout.com specializes in social publishing through one API and local MCP gateway.

The REST API, API-key billing, dashboard, and local MCP gateway are launch-ready surfaces. Individual provider availability still depends on approval, account permissions, and live provider health.

Start with an API key, connect destinations in the dashboard, then call POST /v1/publish for connected and approved destinations. AI-agent users can run the local MCP server with the same API key.