Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
Platforms
Overview
Instagram
Threads
X
LinkedIn
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark
Ctrl k
Search...
Sign up
Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
Platforms
Overview
Instagram
Threads
X
LinkedIn
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap

Roadmap

What is not built yet, and what is deliberately never going to be.
Updated 2d ago
TrademarkTrademark© Dopler. All rights reserved.
Built with Aveiro
Where Chirio is heading. Dates are intent, not commitment.

Not in the product today

Known gaps, listed so nobody builds around a feature that does not exist:
  • Analytics. No read endpoints for per-post insights — impressions, likes, reach. On the list.
  • An OpenAPI spec for /api/v1, machine-readable for both human developers and coding agents.
  • Automatic retry and backoff for transient platform failures. Rate limits and media_processing_timeout currently surface to you as a failed target to retry yourself.
  • A normalised error taxonomy. A rate limit currently reads differently depending on which network produced it — the platform's own message passes through.
  • Annual billing. Monthly only for now.

Coming

Developer experience. The OpenAPI spec, official client libraries, and richer examples than raw fetch. More networks. Ranked by what customers actually ask for rather than novelty — TikTok, Bluesky and YouTube Shorts are the current candidates. Adding one does not change any existing integration: a new platform value, the same endpoints. Analytics ingestion, so you can sync per-post performance back into your own product.

Permanently out of scope

Not "later" — never, because they belong in whatever you build on top:
Why
**Media hosting**Storage, CDN, scanning and retention are their own product
**Scheduling**You own the clock; a scheduler is one cron away on your side
**Outbound webhooks**Poll `GET /api/v1/posts/:id` for targets still settling
**Analytics dashboards**Ingestion may land; the UI on top of it will not

Requests

If something here matters to your integration — or something missing from it does — say so. What customers ask for is what moves up this list.