Publish anywhere from one endpoint.
Connect your social accounts once, get an Open REST API + hosted MCP server, and publish from n8n, Make, Zapier, or your own AI agent. A lightweight connectivity layer with no bloated dashboard and no built-in AI.
LinkedIn, YouTube and X publish today. TikTok and Instagram have published real posts and are waiting on platform review before they open to everyone. Threads and Facebook are built and connectable, but have not yet been proven against the live platform.
POST /v1/posts
Authorization: Bearer ***
{
"accounts": ["tiktok:acc_123", "linkedin:person:Fyv"],
"content": "New drop is live \u23f0 #fyp",
"media": [{ "url": "https://cdn.you.com/teaser.mp4" }]
}What you are actually integrating
What you take on by wiring them yourself
Every figure below is a property of the platforms themselves, not a competitor's price list. Connecting them directly means owning all of it.
OAuth flows to build and keep working
Instagram, Threads, TikTok, Facebook, LinkedIn and YouTube each authorise on a different host, with their own token lifetimes and refresh rules.
Media rules to encode
TikTok takes video only. LinkedIn rejects a second media item rather than truncating. Threads counts 500 characters as UTF-8 bytes, so an emoji costs four.
App reviews to file and pass
Publishing permissions are gated behind review at TikTok, Meta, Google and LinkedIn. We carry those submissions so you do not open a developer account.
Code to change when a platform is added
Adding a channel changes an account reference in your request. The shape does not move.
Counts come from this product's own adapters and from each platform's published documentation. Nothing here is a comparison against another tool. 4 of 7 channels are in review right now, and we carry those submissions.
How it holds together
Why one request shape survives seven platforms
The differences live in adapters
Each platform gets exactly one adapter. Nothing platform-specific leaks into routes, jobs or the API, so the seventh channel costs what the second did.
Partial success is a real answer
Publishing to four accounts routinely half works. You get a per-account result, not a single boolean that hides which one failed.
Failures are specific
An expired token, a rejected media type and a rate limit need three different fixes, so they return three different errors rather than one generic failure.
One API, every platform
Connect an account once. Publish with one uniform request shape, so adding a platform never changes your code.
REST + hosted MCP
The same API key drives a REST API and a hosted MCP server, so your AI agent can publish without touching any platform portal.
Drop into your stack
Works as a plain HTTP step in n8n, Make, Zapier, or your own agent. Signed webhooks close the loop, so you never have to poll.
We absorb the hard parts
Server-side OAuth + token refresh, creator_info pre-flight, rate-limit pacing, media upload. You send one request.
Supported channels
Seven platforms, one request shape
Each platform has its own media rules, rate limits and approval process. Creasion absorbs the differences so adding a channel never changes your code.
TikTok
Video
Direct Post with creator_info pre-flight, so the options you offer match the creator's own account settings.
Image, video
Professional accounts via the Instagram Login API, no Facebook Page required.
Text, image, video, PDF
Personal profiles today, including PDF document posts, the swipeable carousel format.
YouTube
Video, Shorts
Resumable upload through the Data API, with quota-aware pacing built in.
Threads
Text, image, video
Text-only posts are first class here, plus replies and topic tags.
Text, link, photo, video
Publishes to the Pages you administer: one connection, every Page.
X
Text
Billed per post from prepaid credit, not your quota, because X charges per call. The price is shown before you publish.
REST and MCP
The same key drives both surfaces
Publish over plain HTTP from n8n, Make, Zapier or your own code. Or point an AI agent at the hosted MCP server and let it call the same publish layer directly.
MCP tools available on the hosted server:
- list_accounts
- list_posts
- publish_post
- schedule_post
- get_post_status
Pricing
One flat plan, and X billed per post
Every feature is on every paid plan. Capacity is the only difference, and X is metered separately because X charges per call.
Free
forever
- 2 connected accounts
- 30 posts per month
Pro
per month
- 25 connected accounts
- 3000 posts per month
X is billed from prepaid credit rather than your quota, because X charges us per call and a post containing a link costs more than a plain one. The exact price is shown before you publish. Currently 2 credits for a plain post and 25 for a post containing a link.
See full pricingQuestions
Before you sign up
Which channels can I actually publish to today?+
LinkedIn, YouTube and X publish today. TikTok and Instagram have published real posts and are waiting on platform review before they open to everyone. Threads and Facebook are built and connectable but not yet proven against the live platform. The channel cards above carry the current state of each.
Do I need my own developer account at each platform?+
No. You connect your own social accounts through our OAuth flow. The developer registrations and app reviews are ours.
What happens when publishing partly fails?+
You get a result per account, plus an overall status of published, partial or failed. A signed webhook carries the same detail, so you do not poll.
Is there an AI feature?+
No, deliberately. Creasion is the connectivity layer. Bring your own model, or drive it from an agent through the MCP server.
Why is X priced separately?+
X charges per API call, and a post containing a link costs well over ten times a plain one. Hiding that inside a flat subscription would mean one heavy user paying for everyone else, so it is billed from credit at the real rate.
Ship publishing in an afternoon.
One key. One request shape. REST and MCP together.
Get started