An agent that stops for review

An SEO content agent you can check before it ships

Yes, there is an agent that does SEO content end to end, up to the point where a person should decide. Blogo researches a topic, drafts the article, checks the facts, images and links, and repairs what it can. It then stops with a draft for you to review. It never publishes.

Start with your websiteSee pricing

What runs on its own

Give Blogo a topic, or accept one it recommends, and it can run the rest of the work without a prompt from you. In the app that is one button, “Auto-pilot”, which runs every remaining step with the recommended choices.

  • Research: what the pages that already rank cover, which sources can be cited, and which of your own live pages are worth linking to.
  • A writing plan: page type, target search, audience, scope and what the page must include.
  • Keywords, title and outline, then the draft itself.
  • Images from licensed stock sources, each visually checked against its section and given a credit line.
  • A fact check of the finished text against sources, followed by an automatic repair of what failed.
  • A request to every link in the article, so a dead link is caught before you see the draft.

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. If the plan comes back with warnings, or the topic looks like it needs a product page rather than an article, the run stops until a person has read and confirmed it.
  • 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.
  • Sending to WordPress. A person confirms the exact reviewed text first, and what is created is a draft post.
  • Publishing. That happens in WordPress, by you. Blogo has no publish action.

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.

Both share one limit of 60 requests a minute per key. Repeating a step that already finished does not pay for it twice.

What it does not do

Being clear about the edges is part of what makes the drafts usable.

  • It does not publish, and its article flow does not edit or delete pages already on your site.
  • It does not skip checks when called from the API. An article started from code goes through the same plan confirmation and the same checks as one started in the app.
  • It does not start a rewrite or a second repair pass on its own. Those are choices a person makes.
  • It does not invent your business facts. Details only you know come from your answers or are left out.
  • It does not promise rankings, traffic or indexing. It produces a checked draft; results depend on your site and your market.
  • Blogo creates WordPress drafts only. A person on your team reviews and publishes.

Cost and availability

One new article costs 10 credits, whether it is written from the app, the API or an MCP client; there is no separate fee per call. If no draft is delivered, the credits are returned.

Blogo is in a free, invite-only pilot. Checkout is not open, API access is by invitation, and writing drafts to WordPress is switched off for now, so a finished article is reviewed in Blogo and copied out as Markdown.

Questions

Can the agent publish an article without anyone looking at it?
No. There is no publish action in the app, the API or the MCP server. The furthest Blogo goes is a WordPress draft, and only after a person confirms the reviewed text.
Which AI assistants can use the MCP server?
Any MCP client that supports remote servers with an authorization header. You add the server address and your API key to the client’s configuration; the API documentation shows the exact block.
Can an assistant run a whole article unattended?
It can run every automated step. It will be told to stop when the plan needs a person, when the interview has no answer yet, and when the article is ready for review. Those hand-offs cannot be skipped from code.
Does the API cost extra?
No. API and MCP calls are free. An article written through them uses the same 10 credits as one written in the app.

Watch it run on your own site

Add your website and let Blogo take one article from topic to reviewed draft. Blogo is in a free, invite-only pilot.

Start with your website