How to Test Your Seller URL with Agentprobe

Agentprobe checks whether an AI agent can discover, quote, and complete a purchase on your seller site. You submit a seller URL, it runs 13 probes, and it returns a score plus a readiness tier. Use it when you want a concrete, itemized answer to "can an agent actually buy from me?" rather than a general audit. The output is most useful if you treat the probe list as a checklist and fix the gaps it flags.

What Agentprobe measures

The tool runs 13 probes against a seller URL:

• llms.txt
• OpenAPI
• ai-plugin.json
• MCP
• commerce.json
• catalog API
• quote API
• checkout API
• payment rails
• refund/contact
• unsupported rails
• no fake claims
• fulfillment proof

Each probe maps to a capability an agent needs somewhere in the discover → quote → purchase chain. Missing discovery files (llms.txt, ai-plugin.json, commerce.json) mean an agent may never find you. Missing catalog, quote, or checkout APIs mean it can find you but can't transact. Payment rails, refund/contact, unsupported rails, no fake claims, and fulfillment proof cover the trust and completion side — whether an agent can pay, whether a human can get a refund, and whether your claims are backed by evidence.

Score tiers and what they mean for you

Note the scale in the registry listings runs to 110 (for example, 110/110 and 105/110), while the tier thresholds are stated as ≥85/95. Read the tier as the decision-relevant signal and the raw score as the progress metric. If you land in PARTIAL, the fix is almost always on the transaction side — you're discoverable but an agent can't complete a purchase. If you're NOT_READY, start with the discovery files before touching checkout.

Steps to test your URL

1. Go to agentprobe.fly.dev.
2. Use the "Run probes" action and enter your seller URL.
3. Wait for the probe run to finish. You get a score and a tier.
4. Read the per-probe results, not just the total. Each failing probe is a specific missing artifact or endpoint.
5. Fix the highest-leverage failures first: discovery files if you're NOT_READY or low PARTIAL, then catalog/quote/checkout if you're PARTIAL, then payment and trust probes to push into AGENT_READY and CERTIFIED.
6. Re-run the probes on the same URL to confirm the score moved.

Expected result: a numeric score, a tier label, and an itemized pass/fail list you can work through. The verification method is simply re-running the probe after each change — the score is the feedback loop.

Using the certified registry as a reference

The site lists top certified sites with their scores, and links to a full registry. Current examples include:

• https://agentic-evidence.fly.dev — CERTIFIED 110/110
• https://8bitconcepts.com — CERTIFIED 110/110
• https://agentprobe.fly.dev — CERTIFIED 110/110
• https://nothumansearch.ai — CERTIFIED 110/110
• https://bringyour.ai — CERTIFIED 110/110
• https://geo-agent.fly.dev — CERTIFIED 105/110
• https://pictureperfectprojects321.com — CERTIFIED 100/110

These are useful as working examples: if a probe fails on your site, check how a 110/110 site exposes the same capability. The registry is also the place to see which sellers are already agent-legible in your space.

Common sticking points

• Score scale confusion. Registry entries show /110 while tier thresholds reference /95. Don't assume a 90 means CERTIFIED without checking the tier label.
• Discovery-only fixes. Adding llms.txt alone can move you out of NOT_READY but won't get you past PARTIAL — the quote and checkout probes still need real endpoints.
• Trust probes ignored. "No fake claims" and "fulfillment proof" are easy to skip because they aren't APIs, but they gate CERTIFIED.
• No re-test. The score only helps if you re-run after changes; a single run tells you where you started, not whether you improved.

The tool is versioned (v0.3.1) and exposes an API, a registry, and JSON output, so you can automate re-testing rather than checking manually each time.