Contentosapp Studio – AI Content Writer & SEO (BYOK)
Most AI plugins generate slop. Contentosapp Studio generates article drafts that are built to rank.
Paste a topic. A team of seven specialized AI agents researches it, writes it in your brand voice, checks the sources, prepares the images, and drops a finished draft straight into your WordPress editor for you to review and publish. No copy-pasting from ChatGPT. No generic “average of the internet” output. No hallucinated links.
It runs inside your WordPress dashboard, and it is free and unlimited with your own AI key.
Your 7-agent content team, inside WordPress
Instead of one prompt and one generic draft, each article passes through seven specialists:
- Discoverer – finds the real search intent and the angle competitors miss.
- Strategist – turns that into a brief: SEO structure, keyword map, and the gaps to fill.
- Researcher – grounds the article in real facts, statistics, and source material.
- Writer – drafts the article in your configured language and brand voice.
- Editorial Reviewer – checks quality, structure, and factual consistency, and flags anything to verify.
- Visual Designer – prepares image prompts, visual structure, and Schema.org markup.
- Social Media – turns the finished article into social media copy for distribution.
Bring your own AI key – free and unlimited
Connect your own Google Gemini, OpenAI, or Anthropic Claude key and send requests directly from your site to that provider. There is no plugin markup, no per-article cap, and no local production limit – any limits come from your own provider account, pricing, quota, and terms. Bring Your Own Key mode works without a license.
No AI slop: real research, real links
Claims are grounded in sources the Researcher actually found, not invented. When you add your own reference links, the plugin reads their real content and uses it as grounding material. Internal links point to real URLs, and articles arrive as drafts for human review – the opposite of the thin, mass-produced auto-blogging pattern search engines demote.
Sounds like you, not like a robot
Save reusable Brand Voice settings once – tone, vocabulary, author persona, and examples, plus per-agent customization – and they are applied across the workflow automatically. “On-brand” becomes a setting, not a per-article rewrite. These settings are stored in WordPress and applied to the local workflow.
Publishes safely into WordPress
Articles are stored as production history and published to connected WordPress sites over the WordPress REST API using Application Passwords. You choose the destination site and whether each article is sent as a draft or a published post, so you always keep the final review gate.
Article types
- Pillar articles – long-form reference articles.
- Satellite articles – focused articles for supporting topics.
- Comparison articles – versus-format articles with optional affiliate link support.
- News articles – articles synthesized from source material.
- Content updates – rewrites or updates of existing posts.
Don’t want to manage API keys? Turn on ContentOS Auto
Prefer zero setup? ContentOS Auto is an optional managed service at contentosapp.com that runs the workflow for you – hosted AI processing, managed prompts, managed search/image services, quota tracking, license activation, and account features. The Free plan needs no license or credit card: it includes unlimited Bring Your Own Key usage plus 3 one-time ContentOS Auto trial productions. Limits for ContentOS Auto are enforced by the hosted service.
Languages
Fully available in English (en_US), Español (es_ES), and Português do Brasil (pt_BR). The selected language is applied to the agent workflow and the generated draft.
We use it on our own blog
Every article on contentosapp.com is produced with Contentosapp Studio and edited by a human. The blog is the proof of concept, built in the open.
External Services – Required Disclosure
Contentosapp Studio connects to external services only for the features and providers you configure. The data sent depends on the selected mode, provider, and action.
Contentosapp Studio / ContentOS API (api.contentosapp.com)
Used for optional ContentOS Auto managed generation, managed agent prompts, license activation, quota checks, managed image generation, managed search grounding, hosted job status polling, add-on credit actions, account portal links, and telemetry if you explicitly allow telemetry in the plugin. Depending on the action, requests may include your site URL, plugin version, license/account data, selected settings, usage counters, article briefs, keywords, source URLs, agent prompts, generated output, image prompts, error categories, and technical diagnostic data. Telemetry is not sent until you accept or decline it in the admin UI.
Terms: https://contentosapp.com/terms Privacy: https://contentosapp.com/privacy
Google Gemini / Google AI Studio (generativelanguage.googleapis.com, aistudio.google.com, vertexaisearch.cloud.google.com)
Used when you configure Gemini as an AI provider, test a Gemini API key, discover Gemini models, or use Gemini features supported by your account. Requests may include your API key, selected model, article brief, keywords, prompts, source material, generated context, and image/search prompts when those features are enabled.
When Gemini web search grounding is used, the citation links Gemini returns are vertexaisearch.cloud.google.com/grounding-api-redirect/... redirect URLs. To show the real source of each citation, the plugin sends a lightweight HEAD request to that host to follow the redirect to its final destination URL. Only the redirect URL itself is requested (no API key, article content, prompts, or credentials are sent), and the resolved result is cached. This happens whenever a grounded citation needs to be resolved.
Terms: https://developers.google.com/terms Privacy: https://policies.google.com/privacy
OpenAI (api.openai.com)
Used when you configure OpenAI as an AI provider, test an OpenAI API key, discover OpenAI models, or use OpenAI image features supported by your account. Requests may include your API key, selected model, article brief, keywords, prompts, source material, generated context, and image prompts.
Terms: https://openai.com/policies/terms-of-use/ Privacy: https://openai.com/policies/privacy-policy/
Anthropic Claude (api.anthropic.com)
Used when you configure Anthropic Claude as an AI provider, test an Anthropic API key, or discover Anthropic models. Requests may include your API key, selected model, article brief, keywords, prompts, source material, and generated context.
Terms: https://www.anthropic.com/legal/commercial-terms Privacy: https://www.anthropic.com/legal/privacy
Serper.dev (google.serper.dev)
Used only when you configure Serper.dev as the web search provider and a production step uses web search. Requests include your Serper.dev API key and the search query generated by the agent. Article content, WordPress credentials, and provider API keys for other services are not sent to Serper.dev.
Terms: https://serper.dev/terms Privacy: https://serper.dev/privacy
Tavily (api.tavily.com)
Used only when you configure Tavily as the web search provider and a production step uses web search. Requests include your Tavily API key and the search query generated by the agent. Article content, WordPress credentials, and provider API keys for other services are not sent to Tavily.
Terms: https://tavily.com/terms Privacy: https://tavily.com/privacy
Exa.ai (api.exa.ai)
Used only when you configure Exa.ai as the web search provider and a production step uses web search. Requests include your Exa.ai API key and the search query generated by the agent. Article content, WordPress credentials, and provider API keys for other services are not sent to Exa.ai.
Terms: https://exa.ai/terms Privacy: https://exa.ai/privacy-policy
User-provided reference URLs
When you add external reference links to a production, Contentosapp Studio fetches those URLs directly from your WordPress server (using the WordPress HTTP API) to read their main text and use it as grounding material for the article. Only the URLs you explicitly provide are requested; no API keys, credentials, article content, or prompts are sent to those sites — it is a plain page read, like a browser visiting the link. Requests are restricted to public http/https addresses (private/loopback hosts are blocked), size-capped, and cached. This happens on every plan and in Bring Your Own Key mode, because reading your own reference links is a local feature.
Connected WordPress sites
When you connect a destination WordPress site with an Application Password, Contentosapp Studio communicates with that WordPress site over the WordPress REST API in both directions. The site is a destination you choose and control; there is no fixed third-party domain — it is whatever WordPress address you enter.
- Writing (publishing/updating): when you publish or update an article, the plugin sends the generated content and publishing metadata (title, body, status, categories, featured image) to the selected site.
- Reading (update-existing-post mode): when you choose to update a post that already exists on a connected site, the plugin first fetches that post from the site (a
GETto/wp-json/wp/v2/posts/{id}or/pages/{id}requesting onlyid, title, content, link, date, modified) so the editor agent can revise the current content. This read happens only when you select an existing post to update.
Both directions authenticate with the Application Password you saved for that site, and only public http/https hosts are allowed (loopback/private addresses are blocked). No provider API keys or other sites’ credentials are sent to the connected site.
Generated content and production history are stored in your WordPress database. In Bring Your Own Key mode, content is sent directly to the AI provider you configure. In ContentOS Auto mode, relevant content is processed by the ContentOS API for the hosted service you requested.