Channels
Use
GET /v1/growth/channels to discover which channels are enabled on a deployment and their config schemas. Each project is bound to one channel (reddit today).
Shared concepts
Every channel shares the same core model:Projects
A project is your product’s Growth configuration: target communities, intent thresholds, scan cadence, LLM budget, and draft rules. Create via bootstrap from an App Store app or manually.Opportunities (inbox)
An opportunity is a scored post worth replying to. The pipeline assigns an intent score, urgency (must_reply / browse), buyer stage, and an LLM-drafted reply. You approve or dismiss before anything is published.
Scheduled posts
Scheduled posts are standalone channel posts (not thread replies) queued for a future time. A background worker dispatches due posts; you can also publish immediately.Review-first publishing
Inbox drafts are never auto-posted. You stay in control of tone, timing, and disclosure — especially important on communities with strict promo rules.How it works (all channels)
- Hard dedupe — each source post is processed once per project.
- Per-project LLM budget — auto-pauses scanning when the daily cap is hit.
- Reply linter — flags missing disclosure, generic openers, links, etc. Drafts are surfaced with warnings, not silently dropped.
REST API surface (shared)
These endpoints are channel-agnostic; filter bychannel or projectId where needed:
Channel-specific connect flows live under
/v1/growth/connect/{channel}/… (Reddit today).
MCP tools
Growth is exposed asgrowth_* tools on the Appeeky MCP server. See MCP → Growth Channels.
Channel guides
Reddit Growth
Subreddit scanning, Composio OAuth, inbox replies, scheduled posts, and REST reference.
Reddit account warmup
Build account trust before API posting so Reddit’s spam filters don’t remove your content.
Pinterest Growth
Pins from app screenshots, board picker, scheduling, and screenshot automations.