Research every topic
Read the web and your earlier posts for a new angle.
Solutions
Run your blog on autopilot
Sourced posts in your voice, published through your CMS
Source every claim
Link every claim and number to the page it came from.
Publish through your CMS
Post in your voice under your publish policy.
How a run works
From topic to a sourced post
A sample run, start to finish. It gathers sources, writes a post that cites them, checks every claim, and publishes through your CMS under your workspace's publish policy.
Factories/Marketing run
IdleIllustrative runEarlier posts in your CMS list_content
Sources on the web fetch
Draft postIn your voice
Publish to your CMS
upsert_contentPostBuilt for marketing teams
Sourced posts, published
Each run turns a topic and an audience into a post you can check claim by claim.
Written in your voice
Writes for the audience and voice you set, with a short summary at the top.
A source for every claim
Links every claim and number to its source. It never invents quotes, numbers, or sources.
Your publish policy
Each publish follows your workspace's CMS publish policy. A pending or denied publish is reported with the reason.
Works with your publishing
Research on the web, publish in your CMS
Web research
Reads pages on the web to research the topic, and keeps a link to the page behind every claim.
Earlier posts
Lists and reads past posts in your CMS so a new one picks an angle they have not covered.
CMS publishing
Creates the post in your CMS with status published.
Publish approval
Waits on your workspace's CMS publish policy and reports pending or denied posts as unpublished.
Start from a template
All templates- AI WriterResearches each topic, keeps a source for every claim and publishes a post in your voice through the CMS. Each publish passes the publish approval first.See template
- Technical SEO EngineerStart with Website URL. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.See template
- Technical Claim VerifierStart with Article or claim list + sources. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.See template
Start on Hobby, move to Pro when you need more
Hobby is free with monthly FTAI. Pro is for heavier use. Eligible accounts can start Pro with a 7-day free trial.
What's included:
$1 daily login bonus
Everything in Hobby, plus:
Pay as you go
Multi-member teams
Free viewers
Beta Feature Opt-in
Marketing questions, answered
What a run writes, where it publishes, and who approves it.
Want to discuss your publishing workflow? Talk to us
1Does it publish without approval?
Each publish follows your workspace's CMS publish policy. When a publish is pending or denied, the post is reported as unpublished with the reason.
2Where do the posts go?
Into your workspace CMS as posts. It only lists, reads, and creates or updates content there.
3How are claims sourced?
Every claim and number links to the page it came from. It never invents quotes, numbers, or sources.
4How does it avoid repeating itself?
It reads earlier posts in the CMS before writing and picks an angle they have not covered.
5Can it match our voice?
Yes. You set the topic, audience, and voice, and each post is written in that voice.
6How many posts does a run publish?
One. Each run researches, writes, and publishes one post on the topic you set.
7Does it post to social channels?
No. It publishes posts through your CMS only.
8What does a run return?
The post title, slug, publish status, and the source list.
Get your next post out
Set a topic, audience, and voice, and each run publishes a sourced post through your CMS.