Use cases

Creasion is infrastructure, not an app you log into every day. It sits behind whatever you already use, an automation tool, your own product, or an AI agent, and turns publishing into one HTTP call.

Small teams and solo creators

Scheduling from a spreadsheet

Keep the content calendar where it already lives. A scheduled automation reads the next row, sends one request, and marks the row published when the webhook confirms it. No new dashboard for anyone to learn.

SaaS and creator tools

Publishing from your own product

Let your users connect their own social accounts inside your product, then publish on their behalf. You never register a developer app per platform, never run the approval gauntlet, and never store platform tokens yourself.

Agent builders

AI agents that actually publish

An agent that drafts a caption is only half a workflow. The hosted MCP server gives an agent the publishing half, with the same API key and the same limits, no platform portal, no browser automation.

Brand and social teams

Cross-posting one asset everywhere

Send one video to several accounts in a single request. Each target reports its own outcome, so a rejection on one platform never silently swallows the posts that succeeded.

In n8n, Make, or Zapier

There is no plugin to install. Creasion is a plain HTTP step, which means it works in any automation tool that can send a request, including the one you have already standardised on.

// n8n → HTTP Request node
Method:  POST
URL:     https://creasionapp.com/v1/posts
Auth:    Header → Authorization: Bearer {{ $env.CREASION_KEY }}

Body:
{
  "accounts": ["tiktok:{{ $json.tiktok_id }}"],
  "content": "{{ $json.caption }}",
  "media": [{ "url": "{{ $json.video_url }}" }]
}

The same request works unchanged from a cron job, a Lambda, or a shell script.

From an AI agent, over MCP

The hosted MCP server exposes the same operations as the REST API, authenticated with the same key. Your agent decides what to post; Creasion handles getting it published.

# Point your agent at the hosted MCP server
{
  "mcpServers": {
    "creasion": {
      "url": "https://creasionapp.com/v1/mcp",
      "headers": { "Authorization": "Bearer sk_live_***" }
    }
  }
}

# The agent now has publish tools available:
#   list_accounts, which accounts are connected
#   create_post, publish or schedule
#   get_post, per-account status

Creasion has no built-in AI, and that is deliberate. You bring the model you already trust rather than inheriting ours.

Closing the loop

Publishing is asynchronous, because the platforms are. Rather than polling, you receive a signed webhook when a post reaches a final state, including when it only half worked.

POST https://your-app.com/hooks/creasion
X-Creasion-Signature: t=1756900000,v1=9f86d081...

{
  "event": "post.completed",
  "post_id": "post_01J8ZQ",
  "status": "partial",
  "targets": [
    { "account": "tiktok:701234", "status": "published",
      "url": "https://tiktok.com/@you/video/7312" },
    { "account": "linkedin:person:AbC", "status": "failed",
      "code": "token_expired", "retryable": false }
  ]
}

Note the partial status. Posting to several platforms routinely half-succeeds, so it is a first-class outcome with per-account detail, not an error that hides which posts went out.

Start with one request

Free to start. Connect an account, get a key, and publish from whatever you are already running.

Get an API keyRead the docs