Via Codex
Plan in Codex, publish through Ankk
Turn a launch brief into channel-specific posts, then send scheduled work to the same Ankk publishing contract.
3 free channels · $2/channel/month · API/webhooks included
A cheaper social scheduler with CLI/API access
Connect channels, schedule posts, and see what published, what failed, and which channel needs attention. Use the dashboard, CLI, API, or signed webhooks from the same workflow.
No credit card required · Free plan forever · AI features are a later add-on
3
Free channels
Enough to test real operations
$2
Growth
Per social channel per month
50
Self-serve
Channels supported on Growth checkout
CLI/API
Automation
API keys and webhooks for repeatable workflows
The buying reason is clear
Before the bigger marketing automation vision, Ankk needs to give users a reason to pay today.
Lower cost
Simple pricing as channels grow
Free includes 3 social channels. Growth is priced at $2 per channel per month, so small teams do not need to overbuy.
Hosted scheduler
Run it without self-hosting
No server maintenance or deployment work. Ankk focuses on connection, scheduling, publishing status, and failure visibility as a hosted product.
Status first
See operations before polish
Know what published, what is scheduled next, and which channel needs attention before you dig into anything else.
The daily view should start with operations
People open a social tool to answer one question first: is everything working right now? Ankk puts that buying reason at the front.
- Separate scheduled, published, and failed states
- Track accepted, queued, publishing, published, and failed work
- Review channel performance and operational issues together
- Move failed publishing into retry and diagnosis flows with visible reasons
Published
24
Posts in the last 7 days
Scheduled
18
Posts waiting in queue
Failed
1
Item needing attention
Threads launch update
Today 09:30 · Threads
Instagram product note
Yesterday 18:00 · Instagram
YouTube community post
Token refresh needed · Beta
Supported channels, with status
The useful question is not just what we list. It is what you can rely on today.
CLI/API
For automated workflows, CLI/API is the shortest path
Ankk is not trying to own the full AI-agent marketing workflow yet. Create output in the AI service or script you already use, then hand it to Ankk CLI/API for scheduling, status tracking, and signed webhook events.
- Dashboard for the default user workflow
- CLI/API for repeatable automation users
- API keys and signed webhooks included in the Growth buying reason
$ bunx @anakonn/ankk --json health
$ ankk contents publish --file payload.json --scheduled-for "2026-07-01T09:00:00Z"
AI tools + Ankk
Use Codex, Claude Code, ChatGPT, or your automation stack
The AI tool writes, plans, or runs the workflow. Ankk receives the publishing request, schedules it, and keeps the operational status visible.
These demos show external tools controlling Ankk through CLI/API workflows.
Via Claude Code
Run CLI scheduling from the terminal
Let Claude Code prepare the command, review the payload, and submit content with ankk contents publish.
Via ChatGPT
Draft in ChatGPT, hand off to Ankk
Use ChatGPT for post ideas and refinement, then move approved copy into Ankk for scheduling and status tracking.
Via API automation
Wire scripts and no-code tools into publishing
Send accepted content into Ankk from scripts, schedulers, or automation tools while keeping webhook-driven status.
Automation proof
What the API/CLI/webhook promise means today
These examples stay inside the current product contract: public API keys, async accepted responses, status tracking, signed customer webhooks, and visible failure or retry concepts.
API key
Bearer API keys are part of the product
Free includes 1 API key and 1,000 API requests per calendar month. Growth includes API access subject to fair use.
Authorization: Bearer <api_key>
CLI command
CLI is a thin path into the same workflow
Use the CLI to hand scheduled work to Ankk without treating it as a separate execution plane or promising provider success at command time.
ankk contents publish --file payload.json
Signed webhook
Webhooks are included in the buying reason
Free includes 1 webhook endpoint and 300 webhook deliveries per 30 days. Growth includes signed customer webhooks subject to fair use.
Failure visibility
Accepted work still needs status tracking
Accepted means the request was validated, persisted, and scheduled. Publishing can still move through queued, publishing, published, failed, or retry paths.
Contract-safe status timeline
accepted
Request passed validation, entitlement, quota, persistence, and scheduling.
queued
Provider work is waiting in the persisted execution flow.
publishing
The execution host is attempting provider-side publishing.
published
The provider-backed operation completed successfully.
failed / retry
The work needs diagnosis, retry scheduling, or a visible terminal reason.
A flow Buffer-searching users already understand
We are not explaining a new category. We are solving the social scheduler job more cheaply and directly.
01
Connect social channels
Connect only what the brand needs and validate the workflow with 3 free channels first.
02
Create and schedule posts
Write in the dashboard or bring drafts from external AI tools, then schedule per channel.
03
Track status and performance
Use published, scheduled, failed, and attention-needed states to decide the next action.
Pricing should be understood on the first screen
Start free, then grow only when you add more channels.
Free
For individuals and small starts
$0
- 3 SNS channels
- 10 scheduled posts/channel
- 1 member
- 1 API key
- 1,000 API requests/month
- 1 webhook endpoint
- 300 webhook deliveries/30 days
Recommended
Growth
All core SNS operations
$2 /channel/mo
- Up to 50 self-serve channels
- Scheduled posts included, fair use
- Analytics/API/signed webhooks included
- AI sold later as a separate pack
Custom
For teams managing 51+ channels
Contact us
- 51+ SNS channels
- Custom contract and billing
- High-volume planning
- Onboarding support
AI roadmap
AI automation remains the direction, but paid scheduling comes first
The long-term goal is an AI-automated marketing suite. The current Growth buying reason is social scheduling, operational status, and CLI/API access. AI features stay separated as a later add-on.
- Do not bundle AI into the Growth channel price
- Keep room for a future AI Pack or credit product
- Keep the homepage focused on Buffer/Postiz replacement intent
Looking for a Buffer or Postiz alternative?
Connect 3 channels for free and see whether the scheduling workflow fits before upgrading.
No credit card required · Free plan forever