Enable order status
The sample store can power “Check order status”, but it's turned off, so AI agents can't use it.
Business impact: 54 agent requests asked for this in the last 30 days.
This is a fictional retailer with sample data, shown to illustrate AgentPass. None of these numbers describe a real business. Every number here is computed by the same code that powers real AgentPass dashboards.
Harbor & Pine Outfitters · harborandpine.example · Agent readiness 91 / 100 (58 → 73 → 91)
+75.1%vs. previous 30 days
+71.2%vs. previous 30 days
+80.5%vs. previous 30 days
−0.1 ptsvs. previous 30 days
−4.2 ptsvs. previous 30 days
+2.3%vs. previous 30 days
AgentPass counts only activity that flows through your AgentPass agent interface and orders it can defensibly match to an agent. It can't see every AI conversation about your business.
39% of agent actions came from callers that didn't identify themselves.
Agent names are self-reported: each named agent identified itself in its requests. AgentPass never guesses an agent's identity.
AgentPass shows aggregated, privacy-protected request data: grouped search terms and filters only, never raw prompts. Requests seen fewer than 2 times are hidden to protect shopper privacy.
Agents got stuck 617 times in the last 30 days.
370 shopping sessions requested an item that returned no matching product.
399events66 shopping sessions asked for something your agent interface doesn't offer yet.
66events59 shopping sessions couldn't confirm whether a store had the item they wanted.
59eventsFailed basket value: $2,061 (15 of 20 failed carts with a known value)
These are demand signals, not lost revenue. “Failed basket value” is shown only where a cart's value was known; everything else is counted as lost-demand events.
See all opportunitiesProduct catalog
99.8% of 4,533 agent actions succeeded.
Inventory
98.2% of 1,023 agent actions succeeded.
Cart
99.0% of 832 agent actions succeeded.
Checkout
97.2% of 546 agent actions succeeded (target: 98% or better).
Average response time: 331 ms
Inventory: Slow responses from your commerce system
Inventory checks failed 17 times because your connected commerce system took too long to respond.
Sep 25 · 17 failures
failure_codes: upstream_timeout
http_statuses: 504
protocols: mcp, ucp
capability: inventory
first_seen: 2026-09-25T12:32:53.000Z
last_seen: 2026-09-25T21:30:51.000Z
messages:
- inventory service 504 Gateway Timeout
sample_trace_ids:
- demo-trace-95227d99b1621271
- demo-trace-6442901dc6ea4417
- demo-trace-b976a99d11adb049The sample store can power “Check order status”, but it's turned off, so AI agents can't use it.
Business impact: 54 agent requests asked for this in the last 30 days.
Free scan. No account required.