# I built an AI content agent that would rather drop a topic than make things up > Source: > Published: 2026-10-02 21:20:51+00:00 Most “AI writes your blog” setups fail in the same way: not with bad style, but with a confidently written falsehood. For most niches that is embarrassing. For an insurance website it is a real problem — a wrong sentence about a legal obligation or the scope of cover can mislead a reader. This is how I designed an AI agent for [gopoistenie.sk](https://www.gopoistenie.sk/), a Slovak insurance website (motor liability, comprehensive cover, GAP, home and travel insurance). It prepares one article every week — and it is built so that **a lack of facts is a reason to stop, not a reason to improvise**. The client needed regular content, because an insurance site lives on search: people look up what liability insurance covers or how GAP works, and if your site does not answer, someone else's will. But the real requirements were these: The pipeline starts by itself every Monday at 6:00 with nobody involved: Telling a model to “only use reliable sources” does not work. Giving it a fixed list of sources and refusing to proceed without them does. The research step is the place where hallucinations are prevented — the writing step only has to stay inside the material it was given. Most pipelines treat “no article this week” as a failure, so they are built to always produce something. Here it is a normal, expected result. That single decision removes the pressure that makes generated text drift into made-up specifics. The model that wrote the text is not the step that approves it. A separate review step compares the draft with the sources before it is saved at all — just as with people, an author should not be their own editor. Publishing. The site owner reads the finished article in a dashboard and clicks **Publish** or **Reject**. Nothing else is required — but without that click, nothing reaches the site. That is a deliberate decision, not a technical limitation. The site is responsible for what it publishes, and that responsibility should not be handed to an automaton. The agent saves the work of finding a topic, gathering material and writing; the decision stays with a human. The project is delivered and running every week. The client left a 5/5 review on the independent Slovak freelance portal Jaspravim.sk (in Slovak, translated): *“Maksym built an AI agent that drafts blog articles for regular publishing. A professional approach, prompt communication, and the work was finished quickly with no delays.”* The same pattern — data-driven topic, verified sources, separate check, human approval — works in any field where accuracy matters: finance, legal, health, technical documentation. *Originally published as a case study on [nexflow.sk](https://nexflow.sk/en/case-ai-seo-articles). I build AI agents and automations for small businesses in Slovakia — see also [AI agent vs chatbot vs automation: what your company actually needs](https://nexflow.sk/en/ai-agent-vs-chatbot).*