An agent that stops for review

An SEO content agent you can check before it ships

Use Blogo’s article workflow from the app, REST API or an MCP client. Confirm the plan and provide first-hand answers, then advance the available research, drafting and review steps. The saved article returns to a person for editing and editorial handoff.

What runs on its own

Begin with a topic and confirm the writing plan. In the app, assisted continuation can select recommended choices and advance available steps. The API advances one step per request and tells the client when to stop for your input or review.

  • Reference research using the accessible pages and configured providers available for the topic.
  • A writing plan: page type, target search, audience, scope and what the page must include.
  • Keywords, title and outline, then the draft itself.
  • Optional imagery and its checks when the selected media feature and sources are available.
  • Verification of selected factual claims plus deterministic evidence checks; unresolved issues remain for review.
  • Link checks that report failures and can remain incomplete when a destination cannot be read.

Where it always stops for a person

An agent that never stops is the risk on a company website. Blogo has fixed stopping points, and they hold whether you drive it from the app, the API or an AI assistant.

  • The writing plan: confirm its reader, purpose, boundaries and warnings before paid article work proceeds.
  • Your first-hand input. Before writing, Blogo asks a few interview questions about how your business actually does things. Writing does not start until at least one is answered, and neither the API nor an assistant can answer for you.
  • A paid retry. If a paid step ends without usable output, running it again is new paid work, so only a person can start it.
  • Final review. When the checks are done the article waits in Blogo. Anything a check could not resolve is listed for you.
  • The editorial handoff: the current output is Markdown. An enabled, configured WordPress send requires confirmation of the exact reviewed text.
  • Public publication: your editorial team handles it in the destination CMS.

Drive it from code or from an AI assistant

The same workflow is available outside the app, with an API key you create in settings.

The REST API (v1) has endpoints to list your sites and articles, start an article, draft and confirm its writing plan, and advance it one step per request. Each response says what to do next: advance again, confirm the plan, or hand over to a person in the app.

Blogo is also an MCP server at /api/mcp, so an MCP-compatible assistant can use it directly. The tools are list_sites, list_articles, get_article, create_article, plan_article, confirm_plan and advance_article. There is no publish tool and no publish endpoint.

REST and MCP share a per-key limit of 60 requests a minute within each server instance. Replaying completed work uses its saved result; an explicitly authorized regeneration is different work.

Keep automation tied to the current draft

Use the same confirmed plan, current article and review handoffs whether the workflow starts in the app or from code.

  • New-article work stays separate from the public pages already on your site.
  • API-created articles use the same plan confirmation and review requirements as app-created articles.
  • Choose a rewrite or additional repair explicitly, with the corresponding paid authorization when required.
  • Business details are supplied by your team and checked in context; unresolved statements need your review.
  • The output is a reviewable draft. Rankings, traffic and indexing depend on factors beyond this workflow.

Cost and availability

One delivered new article uses 10 credits from the app, API or MCP client; there is no separate per-call fee. If the write fails before saving a draft, its reserved credits are released. A saved draft can still need review; an explicit rewrite is new article work.

Choose a subscription or a one-time credit pack on the pricing page. API and MCP use the same article credits as the app. Review a finished article in Blogo and copy or download Markdown; export does not require an author. WordPress handoff creates a new unpublished draft only with enabled sending, your configured site connection, a real author, review checks and current-article confirmation. An unchanged version can reuse its saved receipt; changed content can create another draft. Blogo does not automatically publish.

Questions

Can the agent publish an article without anyone looking at it?
The API and MCP have no publish operation. The current handoff is Markdown; an enabled WordPress send creates a draft after the required current-version confirmation.
Which AI assistants can use the MCP server?
The server uses stateless Streamable HTTP with JSON responses and API-key authorization. Use a client that supports that transport and authorization method; consult the API guide for configuration. Individual clients have not all been tested.
Can an assistant run a whole article unattended?
A client can advance the available automated steps. The response directs it to stop for plan confirmation, first-hand interview answers, paid retry or review when required. Provider configuration and account access still apply.
Does the API cost extra?
There is no separate per-call fee. Provider work still uses the account’s guarded article workflow; a delivered new article uses the same 10 credits as the app.

Prepare a workflow you can inspect

Start with your site and article question, then confirm the plan and review the result. Choose a subscription or a one-time credit pack on the pricing page.