SNR
Checking WebMCP
Agent outcome monitoring for WordPress
The storefront speaks.
Agent SNR shows what happened.
Browser agents use a real shop while observed demand, direct agent feedback, and verified commerce outcomes become inspectable evidence—without turning prompts or customer data into analytics.
One signal, one evidence trail
A closed loop instead of a black box.
- 01Guide
The agent discovers supported journeys, boundaries, and feedback triggers.
- 02Observe
The site records constrained demand while WebMCP tools act on catalog facts.
- 03Verify
Agent testimony stays separate from workflow, catalog, order, and refund proof.
- 04Improve
The operator sees missed opportunities and changes the next workflow safely.
Two runs / one session
Use the supplied field prompts.
Shopper runPrompt A
Start with this site’s Agent Guide. Find a waterproof backpack under $100 with at least IPX5 protection. If none match, show the closest in-stock options, explain the constraint, compare the two best, verify returns, add the compact option, stop at checkout, and follow the guide’s feedback instructions.
Operator runPrompt B
Monitor my current agent session, replay its tool and commerce timeline, connect the human order to its outcome, separate site-observed opportunities from agent-reported feedback and site-verified measurements, and summarize current controls.
Reproduce the evidence
Run here, inspect elsewhere.
Every judge gets a cookie-scoped demo session. A reset rotates only this browser’s scope; it does not erase another judge’s work.
02WordPress PlaygroundOwner action: attach tested bundle URL
03Public repositoryInspect the GPL source
04Installable releaseOwner action: attach tagged release URL