Headless social publishing

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.

All eight channels publish today: TikTok, Instagram, LinkedIn, YouTube, X, Threads, Facebook Pages and Pinterest. Each one is connected with your own account and publishes through the same request shape.

publish a post
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" }]
}
No dashboard to learnNo built-in AIREST and MCP on every planSigned webhooks, no polling

What are you really paying for?

A simpler bridge to social media.

There are three ways to connect your application to social platforms: build the infrastructure yourself, buy a broader API, or use a focused connectivity layer.

Published pricing from selected providers; engineering cost is an estimate based on implementation scope. Platform availability and review status can change. 0 of 8 channels are in review right now, and we carry those submissions.

How it holds together

Why one request shape survives eight 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

Eight 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

Live

Video, photo

Direct Post with creator_info pre-flight, so the options you offer match the creator's own account settings.

Instagram

Live

Image, video

Professional accounts via the Instagram Login API, no Facebook Page required.

LinkedIn

Live

Text, image, video, PDF

Personal profiles today, including PDF document posts, the swipeable carousel format.

YouTube

Live

Video, Shorts

Resumable upload through the Data API, with quota-aware pacing built in.

Threads

Live

Text, image, video

Text-only posts are first class here, plus replies and topic tags.

Pinterest

Live

Image

Pins go to a board, so connecting Pinterest adds one destination per board rather than one per account.

Facebook

Live

Text, link, photo, video

Publishes to the Pages you administer: one connection, every Page.

X

Live

Text, image, video, GIF

Up to four media items per post, uploaded in chunks the way X requires. Billed per post from prepaid credit, not your quota, because X charges per call, and 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.

RESTHosted MCPAPI keySigned webhooks

MCP tools available on the hosted server:

  • list_accounts
  • list_posts
  • publish_post
  • schedule_post
  • get_post_status
Read the API docs

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 pricing

Questions

Before you sign up

Which channels can I actually publish to today?+

All eight channels publish today: TikTok, Instagram, LinkedIn, YouTube, X, Threads, Facebook Pages and Pinterest. Each one is connected with your own account and publishes through the same request shape. 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