CFContentFlow
API DocsStart Building
Content operations for teams that publish at volume

1 Topic 18 Platforms. AI does the rest.

ContentFlow turns one brief into generation, distribution, and comment response workflows. Run yt-factory video jobs, fan them out across 18 platforms, and keep replies moving without a dozen disconnected tools.

Start with BuildRead the API docs
18supported platforms
1 APIfor posts, videos, accounts, and analytics
24/7comment collection and automated replies
Live pipeline
TopicVideoAuto-publishComments
  • yt-factory generation engine
  • OAuth-secured publishing adapters
  • Content Bomb transformation
  • Comment Autopilot reply loop
Platform coverage

18 platform logos, one operating layer

The current stack covers the channels serious media and growth teams actually need, including the Korea and Japan-specific endpoints most generic schedulers skip.

YTYouTube
TTTikTok
IGInstagram
XX
INLinkedIn
FBFacebook
THThreads
PTPinterest
RDReddit
BSBluesky
SCSnapchat
TGTelegram
WPWordPress
GBGoogle Business
NBNaver Blog
TSTistory
KKKakao
NOnote.com
Core workflows

Built for the full content loop, not just scheduling

Content Bomb

Turn one topic into a full platform campaign.

Generate channel-specific angles, headlines, hooks, thumbnails, tags, and repurposed copy from a single brief.

One request fans out into shorts, reels, captions, and blog-ready assets.
Comment Autopilot

Stay present in the replies without living in the inbox.

Collect comments across supported platforms, draft AI replies in brand voice, and keep community response times under control.

Ideal for teams running many channels with small ops bandwidth.
Viral Score

Prioritize the ideas most likely to travel.

Score topics before production using packaging quality, spread potential, platform fit, and hook strength so your team publishes fewer low-leverage pieces.

Use it to decide what gets produced first and what gets dropped.
SDK quickstart

Python and JavaScript examples that match the API shape

Use the Python SDK today, mirror the same flows in JavaScript, and move from topic input to publish-ready assets without custom glue code.

Python SDKpython
01from contentflow import ContentFlow
02
03client = ContentFlow(api_key="cf_live_...")
04
05job = client.videos.generate(
06    topic="DUI 3-strike laws",
07    mode="legal",
08    language="ko",
09    auto_publish={
10        "enabled": True,
11        "platforms": ["youtube", "tiktok"]
12    }
13)
JavaScript SDKjavascript
01import { ContentFlow } from "@contentflow/sdk"
02
03const client = new ContentFlow({ apiKey: "cf_live_..." })
04
05const post = await client.posts.create({
06  text: "Ship once. Distribute everywhere.",
07  platforms: ["youtube", "instagram", "threads"],
08  media_urls: ["https://cdn.example.com/video.mp4"]
09});
Docs + reference

Ship the landing page and the API story from the same deployment

The new `/docs` route covers auth, endpoints, SDK usage, and webhook events. Keep marketing and implementation guidance in one place instead of splitting users across separate tools.

Open documentation
Pricing

Choose the operating range your team needs

Free

For testing API flows and validating your first publishing pipeline.

$0/month
  • 2 social sets
  • 20 posts / month
  • 3 AI videos / month
  • FastAPI reference access

Build

For solo operators and lean teams shipping content every week.

Recommended
$29/month
  • 5 social sets
  • 200 posts / month
  • 20 AI videos / month
  • Content Bomb + Comment Autopilot

Scale

For brands running cross-platform programs with measurable output targets.

$79/month
  • 20 social sets
  • Unlimited posts
  • 100 AI videos / month
  • Priority support and analytics

Enterprise

For agencies, media ops, and internal teams with governance requirements.

Custom
  • Unlimited social sets
  • Unlimited posts and videos
  • Custom SLAs
  • Private onboarding and roadmap access
Customer proof

Placeholder testimonials ready for production copy

“Placeholder: ContentFlow replaced three brittle scripts and turned our publishing queue into an actual operating system.”

Alex MorganGrowth Lead, Placeholder Studio

“Placeholder: The team moved from one-off posting to repeatable topic pipelines without adding headcount.”

Jiwoo ParkHead of Content, Placeholder Media

“Placeholder: We finally had one layer handling generation, distribution, and response workflows across regional channels.”

Mina ChenMarketing Ops, Placeholder Labs
FAQ

Questions teams ask before replacing fragile workflows

Is ContentFlow only for video teams?

No. The system is designed for mixed formats: short-form video, text posts, captions, carousel copy, blog handoff, and automated community workflows.

How does video generation fit into the workflow?

Video jobs run through the yt-factory engine, return an output URL, and can auto-create a publish job when generation completes.

Do you store platform OAuth tokens securely?

Yes. Tokens are stored server-side and encrypted with AES-256 before persistence. Refresh flows re-encrypt updated tokens automatically.

Can we start with one platform and expand later?

Yes. Teams commonly begin with YouTube or TikTok, then layer in the rest of the platform set as operating capacity grows.

What replaces the existing contentflow-lovat.vercel.app site?

Deploy the landing app as the Vercel project root. That swaps the current site for this new marketing and docs experience without touching the API service.