How Agentrix works

Four steps

1. Pick a path — view the public demo, request assisted diagnosis, or run the command yourself. Zero-knowledge users usually start with the demo or an assisted request.
2. Fill in the form — just the target site URL, confirmer name, and consent date. Demo and assisted paths skip this entirely.
3. Diagnose the site — a real agent walks a real browser through signup → browse → cart → pre-checkout. It never completes a purchase, only checks whether the flow is passable. CAPTCHA stops the run.
4. Share the report — Agentrix Score, failure reasons, and fix hints in one document (plus screenshots when captured).

A real example is published in our Shopify demo-store diagnosis: 13 actions, $0.53, stopped by CAPTCHA on the signup form.

Turning a report into a conversation

Share the report on screen and use it as the basis for a few questions:

• Looking at this score, which step matters most to fix first?
• Is bot verification, missing form labels, or forced signup already a known issue internally?
• Where does an agent stopping cost you — search, chat, somewhere else?
• If it reaches pre-checkout, who owns calling that a success?
• Can we set a target score and deadline for the next re-run right now?

Continuous monitoring (paid plans)

Sites keep changing, so a single score goes stale fast. Starter/Business/Agency plans automatically re-scan on a cadence based on plan and site count, and email you if the score drops. See Pricing for details.