Skip to content
Nichr
AI agentsNew techTop 12% of today's analysed ideas

Verification layer so AI agents can prove 'done'

Build a verification and audit layer for AI agents that make changes to live systems (websites, CMSs, codebases, databases): after every write action, it re-reads the live state, diffs it against the intended change, and only then lets the agent report done. Sell it as a drop-in SDK or middleware to teams building agentic automation (marketing agents, DevOps agents, RPA bots) who need trustworthy completion signals and an approval gate before anything goes live.

via Reddit
Original post

What to build

A verification middleware/SDK for AI agents that write to live websites, CMSs, or codebases: after every agent write action it re-reads the live state, diffs it against the intended change, and only then lets the agent mark the task done. Target buyers: teams building marketing agents, DevOps agents, and RPA bots.

Agentic automation that writes to live systems has no reliable way to confirm a change actually landed, so agent 'done' reports can't be trusted without a human checking manually.

Demand

Builders of agentic automation (marketing, DevOps, RPA) need trustworthy completion signals before changes go live, and at least one founder has already hit this exact wall while building agents that edit live websites.

  • Reddit r/microsaasAnecdote

    Founder of Breevy, an agentic website-editing product, posts that the hardest part of building agents that change live websites was proving the change had actually landed.

Stack

  • Playwright
  • diff-match-patch or jsondiffpatch
  • Temporal or BullMQ for retry/verification queues
  • Postgres for audit log
  • Stripe for metered billing
  • Webhook/REST SDK (Node + Python clients)

Solo + AI difficulty

The read-diff-confirm loop is buildable solo in a few weeks for one domain (e.g. CMS/HTML diffing); the hard part is generalizing diff semantics across CMSs, databases, and codebases without false positives/negatives. MVP: 2-4 weeks for a single-vertical (web/CMS) version.

Entry threshold
A solo builder can ship a wrapper library or API that performs post-write verification and human-approval gating for a specific stack (e.g. CMS/SEO agents, or general web agents) in a few weeks; the main cost is integration work per platform, not infrastructure or licensing.
Window
6-12 months

Where to find first users

  • r/microsaas
  • r/devops
  • Product Hunt launch
  • Indie Hackers forum

Counter-signals & risks

  • Many agentic frameworks already ship basic post-action checks (HTTP status codes, screenshot diffs) that teams may consider good enough, reducing willingness to pay for a dedicated verification layer.

  • Verification is highly domain-specific (CMS vs database vs codebase diffing need different diff semantics), which fragments the market and raises integration cost per vertical.

  • A mandatory re-read-and-diff step adds latency and infrastructure cost to every write action, which may be unacceptable for high-throughput automation use cases.

Original title: We built agents that change live websites. The hard part was proving the change landed

Related signals

  • AI agents#10

    Hosted no-code layer on cheap open-source browser agents

    Package pre-built fastbrowse automations as a hosted micro-SaaS for non-technical users: a library of ready browser-agent tasks (price monitoring, form filling, lead scraping, QA testing of web flows) with a dashboard, scheduling, and no-code task builder, charging a markup over the already-cheap LLM cost. Target solo marketers, agencies, and indie devs who want browser automation without running CLIs or managing API keys.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Hacker News
    22 competitors
  • AI agents#6

    Governance and monitoring layer for back-office AI agent workflows

    Package pre-built, department-specific back-office automation workflows (finance, HR, ops, support) for Claude/agent frameworks into a productized template or marketplace a solo builder can sell to SMBs — plus a thin SaaS layer for testing, monitoring and access-control/policy enforcement of deployed agent workflows, since builders in this space are explicitly asking how others test and guardrail agent actions.

    Demand
    5/10
    est.
    Buildability
    7/10
    est.
    Competition
    10/10
    est.
    via Reddit
    0No named competitors
  • AI agents#8

    Proactive agent template as base for vertical AI products

    Use OpenDuet's open-source proactive-agent template to build vertical AI agent products that work in the background and check in with the user at key decision points, instead of pure chat. Target a specific workflow (recruiting pipeline follow-ups, customer support triage, deal/CRM monitoring) and ship a packaged agent with built-in human-in-the-loop checkpoints, sold as a niche micro-SaaS rather than another general chatbot.

    Demand
    9/10
    measured
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via GitHub
    22 competitors
Verification layer so AI agents can prove 'done' — Nichr