One workspace for every client site
Add each client as a site. Each site has its own voice, delivery, Beats and AI visibility, and a person approves every article before it leaves.
Set up once per client
Voice
Tone, spelling, words to avoid and words to prefer, and a style guide, kept for that client’s site.
Illustration style
A palette and a caption for that site, confirmed once and used for every image.
Delivery
To that client’s WordPress, always as a draft, or to a signed webhook.
Beats and schedule
The topics Brenzuri watches for that site, a weekly credit budget, and the days articles are due.
Your team
Owner, Editor, Writer and Viewer. Only an Owner or an Editor can approve an article. Each person can be given some sites and not others.
What your client receives
Every article exports as PDF, DOCX or Markdown. The header carries the client’s brand name, and no Brenzuri wordmark appears in the file. The source list and the version history come with it.
Sources: europa.eu (official) · Reuters · AP · Politico · The Guardian
Generated with sources · reviewed by a human: yes · Approved by Maya Chen, version 3
Agents and API
API keys can be limited to one client’s site, with the scopes brief, generate, read, edit and export. Over MCP an agent can read a site, write a brief and a draft, add sources and languages, and export. It has no approve tool: an agent can write a draft, and a person approves it.
AI visibility per client
Each site’s buyer questions are asked to ChatGPT, Claude, Gemini and Perplexity every week. How it works · Run a free AI citation check
