Social media on autopilot.
Your team works in the dashboard; your AI agents, CI pipelines, and no-code workflows use the API. Publish to Instagram, X, LinkedIn, TikTok, and more, with MCP, CLI, and SDK in the box.
Free plan · no credit card · first automated post in 5 minutes
Driven by the tools you already use
// no humans were needed
› ▌
✎ drafting · "Dark mode is here 🌙 Flip it on in Settings → Appearance"
agent → publish_content({ connections, scheduledAt })
instagram-beaconhqscheduled
x-beaconhqscheduled
linkedin-beaconhqscheduled
— set for 9:00 AM — review it on the calendar anytime
// the deck
Everything an agent needs. Nothing it shouldn't have.
Wire it up once — publishing, retries, and team control all live behind the same API key.
Connect accounts once
OAuth your socials into a workspace. Tokens encrypted, refreshed automatically.
Hand your agent one key
Just an API key — it never sees accounts, tokens, or passwords.
Publish everywhere
One call fans out to every connection by slug.
On autopilot in 5 minutes
Hand your agent the MCP server, drop the CLI into a pipeline, or call the API directly.
// Claude, Cursor, or any MCP client — .mcp.json
{
"mcpServers": {
"socifyr": {
"command": "npx",
"args": ["-y", "@socifyr/mcp"],
"env": {
"SOCIFYR_API_KEY": "sk_..."
}
}
}
}
// then just ask: "Post our launch everywhere"# Install
npm install -g @socifyr/cli
# Configure once
socifyr configure --key sk_...
# Post to multiple platforms
socifyr post "We shipped v2.0!" --to instagram-mybrand,x-myhandle,linkedin-myhandle
# Check status and retry
socifyr status cnt_xyz789
socifyr retry cnt_xyz789import { Socifyr } from '@socifyr/sdk'
const socifyr = new Socifyr({
apiKey: process.env.SOCIFYR_API_KEY,
})
// One call, every platform — schedule with scheduledAt
await socifyr.uploads.text({
connections: ['instagram-mybrand', 'x-myhandle'],
text: 'New post from the SDK',
})curl -X POST https://api.socifyr.com/api/content/text \
-H "Authorization: Bearer sk_your_key" \
-H "Content-Type: application/json" \
-d '{
"connections": ["instagram-mybrand", "x-myhandle"],
"text": "CI build complete — new feature is live!"
}'
# → { "success": true, "data": { "id": "cnt_xyz789", ... } }One key, not ten logins
Connect your socials once with OAuth. From then on, an agent needs just one API key — and never sees a token or password. Revoke the key, and it's out.
SOCIFYR_API_KEY=sk_••••••••••••
Accounts are addressed by slug, not by credentials:
instagram-mybrandx-myhandlelinkedin-mybrandAI drafts, your team approves
An agent saves its work as drafts or schedules ahead — a teammate reviews in the dashboard and publishes, edits, or cancels before anything goes live.
Built for real failure modes
- Structured errors, idempotent retries
- HMAC-signed webhooks on completion
- Timezone-aware scheduling
Humans supervise, roles enforce
Owners manage keys, editors publish, contributors draft. One shared history shows every post — from people and pipelines alike.
// automation
Jobs people stopped doing by hand
Every card below is an hour a week someone got back. Yours is in here somewhere.
Your agent drafts, you approve
Claude writes the week’s posts into drafts overnight. Monday morning, your editor reviews the queue, tweaks two captions, and publishes — AI speed, human judgment.
Ship at 2 a.m., announced by 2:01
A deploy lands overnight. GitHub Actions posts the release to X, Bluesky, and Threads before you wake up.
Write once, post everywhere
A new article goes live — an n8n or Make flow turns it into a post on LinkedIn, X, and Facebook without a copy-paste.
Any trigger becomes a post
Form submission, new product, Stripe sale — one n8n or Make node turns any event into a social post.
A month of content in one sitting
Queue 60 posts with timezone-aware scheduling. Every account posts at its own audience’s 9 a.m.
One platform fails, nine don’t wait
Instagram hiccups while the rest succeed. Retry just the failed channel — no duplicates, ever.
// in production
Built in the open, used in production
Early teams already publish through Socifyr. Here is what they say, how other teams use it, and what you can check for yourself.
How teams use Socifyr
example workflows
also included
A dashboard for the humans
The same API, with a visual interface on top. Compose posts, browse media, track per-channel results, and manage who on your team can do what.
- Compose and preview across platforms
- Media library with reuse
- Publishing history and per-channel results
- Team workspaces and roles
// the edge
Why developers choose Socifyr
What sets it apart from Ayrshare, Zernio, and the rest of the field.
Reliability you can prove
Per-channel retry, idempotency keys so a retried post never duplicates, and structured errors with plain-language reasons. Live per-platform success rates on a public status page.
Agents never see your tokens
An agent gets an API key, nothing more. It publishes by slug and never touches your account credentials. Revoke the key and its access ends instantly.
Every surface, every plan
MCP, REST, CLI, and a TypeScript SDK ship on all plans, including free. The whole developer surface is there from day one, not gated behind an enterprise tier.
Flat pricing that stays flat
$12 for five connected accounts, $39 for twenty, $99 for fifty. No per-account meter that climbs as your team grows, and every plan includes a monthly X allowance.
Bring your own AI
Socifyr doesn't resell AI. Your agent (Claude, Cursor, ChatGPT) writes the post and Socifyr publishes it. The optional caption helper in the dashboard runs on your own provider key, so your content never routes through a shared key.
Weighing the options? See how Socifyr compares to Ayrshare, Zernio, Upload-Post, and Blotato.
// pricing
Free to start
No credit card. Start free, upgrade when your workflow grows.
Add-ons on paid plans: +5 connected accounts for $5/month (stack as many packs as you need) · 100 extra X posts for $5, one-time, credits never expire.
An X post with a link counts as 5 X posts, because X charges more for link posts. Paid post limits are fair-use ceilings, not hard caps. AI is bring-your-own-key on every plan.
// faq
Agent questions, answered
The things people check before pointing an AI at their social accounts.
How does an AI agent post through Socifyr?
Add the Socifyr MCP server to your agent’s config (one npx command). The agent discovers tools like publish_content and list_connections, and from then on "post our launch to Instagram and X" just works — the agent picks the accounts by slug and publishes.
What credentials does my agent need?
Just a Socifyr API key. The key belongs to one workspace, so nothing else is needed. Your social accounts are connected once via OAuth in the dashboard — the agent never sees tokens or passwords, and revoking the key cuts off its access instantly.
Which AI tools work with it?
Anything that speaks MCP — Claude (Desktop and Code), Cursor, and other MCP clients. Agents built on custom stacks use the REST API or TypeScript SDK; n8n, Zapier, and Make connect through the API as well.
Can AI write the posts too?
Yes, with your own key. Socifyr has built-in caption and hashtag generation — bring your own key from OpenAI, Anthropic, Google, Mistral, or xAI and it runs on your own account through the MCP server, CLI, SDK, or dashboard. Or skip it and let your own agent — Claude, GPT, your model — write the content and send it in. Either way Socifyr handles validation, scheduling, fan-out, and delivery.
Which platforms can an agent publish to?
Instagram, Facebook, YouTube, X, LinkedIn, TikTok, Threads, Bluesky, Pinterest, and Reddit — all through the same call.
What happens when one platform fails?
Each platform is tracked as its own channel with its own status. If Instagram hiccups while nine others succeed, you retry just the failed channel — idempotency keys guarantee no duplicate posts.
Can my team supervise what agents publish?
Yes — this is the recommended setup. Have your agent save posts as drafts and let an editor review and publish them, or let it schedule ahead and check the calendar before posts go live. Teammates join with role-based permissions, and the history shows every post with per-channel results, whether a person or a pipeline created it.
How is this different from Ayrshare or Buffer?
Buffer and similar schedulers are dashboards built for humans. Ayrshare is an API, but its paid plans start at $149/month (see the Ayrshare comparison page for details and the date we checked). Socifyr gives you the MCP server, CLI, SDK, and a full dashboard on every plan — starting free.
Tonight’s post could publish itself.
Set it up now, wake up to the announcement already live. Every post you publish by hand is a workflow you haven’t automated yet.
18
platforms
1
API call
5 min
to first post
No credit card. 5 posts a month on us, forever.