Content writer

Blog articles written only from what your product really does. Every article waits for your approval, then can go to your own website.

In the appPlatformSettingsContent writer

The content writer writes blog articles that help your readers and bring people to your website from search. It writes only about what your product really does. A person approves every article before it is published.

You review the articles on the Articles page. See Reviewing an article.

How it works#

It works in three steps. Each step is a separate run of the agent.

Step	What it does	What it can see
Market research	Looks at the public web: who else writes about your field, what your readers ask, and what nobody answers well.	Only public web pages, your platform's name, your public website, your audience and your writing guidance, and the titles you already published. Nothing private.
Ideas	Suggests topics, each with who it is for and what a reader would search for.	Your help pages, About your system, the product's repositories (read only) and the research. No web access.
Writing	Writes one article and lists what each claim is based on.	The same as for ideas. No web access.

Research runs before a batch of ideas when there is none yet, or when it is more than two weeks old. Text found on the web is treated as information only, never as instructions.

The Content writer page#

Only owners and admins can open and change these settings.

At the top, a label says how the writer is doing:

Off: it writes nothing new.
Ideas waiting, with how many, such as 3 ideas waiting: ideas wait for you to choose. A Choose ideas button takes you to the Articles page.
On: it's working, and nothing waits for you.

Under it, a line shows what the writer is doing now, or why its last run failed.

The page has three tabs: Settings, Publishing and Market research.

Switch it on#

1
Go to Settings › Content writer, on the Settings tab.
2
Under Writing, switch on Writing articles for this platform.
3
Under How it works, choose a way to work (see below), and under How many, how many.
4
Under Readers, describe Who reads the articles. Under Style, say How to write: tone, spelling, topics to avoid, words you never use.
5
Under Your website, add your Public website. It is used for market research only.
6
If the platform has more than one repository, tick the ones under This product's code: the ones with this product's code and help pages. The writer reads only those. With none ticked, it reads them all.
7
Click Save.

Switching it off stops new ideas and articles. Articles already written stay as they are.

Your help pages decide what it writes about

The writer describes only what your own help pages (and About your system) describe. It uses the code to check details, never as a source of new features. If a feature is missing from your help, it won't appear in an article. Add it to your help first.

Two ways to work#

Choice	What happens
Suggest ideas for me	When no ideas are waiting, it suggests a new batch, at most once a week. Under How many, choose Ideas in each batch (3 to 20). It only writes the ideas you pick.
Write automatically	It picks topics and writes them by itself. Under How many, choose Articles per week (1 to 14). Each article still waits for approval.

Either way, nothing is published until a person approves it.

You can also ask for ideas at any time with Suggest more ideas on the Articles page, or add your own topic with Add your own topic.

Market research#

The Market research tab shows what the writer found on the public web, with the date of the latest research:

Others writing about it: other sites in your field, with links, and what they cover.
What readers ask: questions seen on the web, with a link to where each was seen.
Nobody answers these well: gaps worth writing about.
What people search for: search phrases.
Notes: anything else the research noted.

It looks again every two weeks, before new ideas. While the writer is on, click Research again to look at the market now. New ideas follow straight after. Before the first batch of ideas, the tab says No research yet.

Style checks#

Each article is checked for writing that reads badly or should not be published. The checks look for:

phrases that sound machine-written, such as "delve", "unlock", "seamless", "robust", "leverage", "game-changer", "in conclusion" and "in today's fast-paced world";
long dashes;
an article that opens with a question;
something that looks like a file path from your code;
something that looks like a key or password.

Anything found is listed under Worth a second look on the article. The checks never change or block an article. You decide.

Publishing to your website#

When you approve an article, it can be sent to your own website. Leave the address empty to publish nowhere: the article is then only marked as published here.

1
Open the Publishing tab.
2
Under Your website, enter the Address for articles. Your developer sets this up. It must accept a signed POST request.
3
Click Save.
4
Copy the Signing secret shown once, and store it on your website. Click Done when you have it.
5
Under Check it works, click Send a test to check your website answers.

After that, Signing secret shows a green Saved label. Click New secret to make a new one. The old one stops working at once. If you change the address, save it before you send a test.

What your website receives#

A signed POST request, signed the same way as replies to your ticket system. See Check the signature.

{
  "type": "article.published",
  "article": {
    "id": "art_…",
    "slug": "how-to-take-deposits-for-venue-bookings",
    "title": "How to take deposits for venue bookings",
    "summary": "One or two sentences for listings and search results.",
    "body_markdown": "## When to ask for a deposit\n\n…",
    "keywords": ["venue deposit", "booking deposit"],
    "published_at": "2026-10-05T09:12:00+00:00",
    "updated_at": "2026-10-05T09:12:00+00:00"
  },
  "platform": { "id": "ten_…", "name": "Your platform" }
}

Store it under article.id (or slug) and show it. The text is Markdown, without the title.
Publishing the same article.id again replaces it.
When someone unpublishes an article, the same address receives article.unpublished with the same shape, and published_at is empty. Remove or hide it.
Send a test sends article.test.
Answer with a 2xx within 10 seconds. Failed sends are retried for about a day.
Ignore any type you don't know, with a 2xx.

The list of what each claim is based on is never sent to your website.

The Cerberius Agents blog

If the Publishing tab says Published articles also appear on the Cerberius Agents website blog, this platform's published articles also appear at the blog on our website. Our team chooses which platform that is.

Notifications#

Under Settings › Notifications, switch on Article ideas or Article ready for any channel. A content writer run that fails is sent as Investigation failed. See Platform notifications.

What it never does#

It never publishes anything without a person approving it.
It never makes up features. It writes only about what your help pages and About your system describe, and lists what each claim is based on.
It never reads another product's repositories when you tick this product's own.
Market research never sees your code, your settings or anything private.
It never changes your code or your systems.
It never sends its list of sources to your website.