Who uses this
- Ecommerce-agent vendors prioritizing which merchants their agents can transact with today vs. need manual workarounds.
- Research teams tracking agentic-commerce adoption over time.
- Sales teams identifying prospects with high demand and low readiness (the ripest integration targets).
What you get
- On-demand scans — POST a domain, get a full report in 2–5 seconds.
- Batch scans — upload a CSV or JSON array, poll for progress, retrieve results.
- Prospect intelligence — opportunity scores combining demand signals with readiness gaps, sortable by category/region, CSV-exportable.
- Synthetic shopping tests — end-to-end agent checkout runs with per-step success/blocker reporting.
- Audit trail — every credit charge links to the scan it paid for via
request_id; no second call needed to answer “what did I get for this charge?” - Reads span the shared scan corpus. When you request a domain, you see the freshest scan anyone has run — not just yours. Your own scan requests are billed to you.
How to integrate
Five supported access modes — pick the one that fits your stack:Pricing model
Credits are the unit of consumption. Reads are free; writes cost credits:
See Credits & billing for the ledger, balance API, and top-up flow.
Next steps
- Quickstart — install the SDK, run your first scan in under five minutes.
- SDK reference — typed methods, errors, retries, batching.
- Authentication — API key and SSO-JWT paths.
- Data model — the full
MerchantScanshape.