One API for social publishing

Every product eventually grows the same feature request: "can it post to our socials?" And every team that says yes discovers the same iceberg. Instagram wants a Business or Creator account and a Meta app review. Threads has its own API with its own quirks. X meters writes on a paid tier. LinkedIn distinguishes personal profiles from company pages. Each platform has its own OAuth dance, its own token expiry rules, and its own media requirements. Chirio exists so you never have to learn any of that.

What Chirio is

Chirio is a multi-tenant social publishing API. You connect your users' social accounts through hosted OAuth, then publish to any combination of platforms with one call:

curl -X POST "$CHIRIO/api/v1/posts" \
  -H "Authorization: Bearer $CHIRIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Launch day!",
    "mediaItems": [{ "type": "image", "url": "https://cdn.yourapp.com/launch.jpg" }],
    "platforms": [
      { "platform": "instagram", "accountId": "8f2c..." },
      { "platform": "threads", "accountId": "91ab..." }
    ]
  }'

That's the whole publishing surface. One bearer key, one JSON body, one to ten targets per call.

The three problems it removes

Problem	What it costs you	What Chirio does instead
OAuth apps and platform review	Weeks of app setup, review submissions, and scope debugging per platform	Hosted OAuth: request an authUrl, send your user to it, get an accountId back
Token lifecycle	Refresh jobs, expiry edge cases, revocation handling, secure storage	Chirio stores and refreshes tokens; your API never sees them
Per-platform publishing rules	Media processing, caption limits, carousel rules, rate limits	One request shape; Chirio translates per platform and reports per-target results

How connecting works

Account connection is a three-step handoff:

POST /api/v1/accounts/connect with a platform and an optional profileId — your own grouping key, typically your user or workspace id.
Send your user to the returned authUrl. They authorize on the platform itself — credentials never touch your app.
They land back on your redirectUrl with ?status=success&accountId=... — store that accountId and target it when publishing.

Tokens live on Chirio's side and are never exposed through the API. Disconnecting an account deletes them.

Who it's for

Chirio is built for products that need publishing as a feature — SaaS dashboards, creator tools, agencies, and increasingly, AI agents that draft content for human approval. If your roadmap says "social integration" and your team would rather ship your actual product, that's the gap Chirio fills.