Skip to main content
Prospect endpoints combine readiness data (from scans) with demand signals (public intelligence, synthetic tests, AI search mentions, telemetry) to produce an opportunity_score — the product of demand and readiness gap:
High opportunity = the merchant is getting agent interest and would benefit most from an agentic-commerce integration.

GET /v1/scanner/prospects

Scope required: read   Cost: 0 Query parameters:
Each prospect is a ProspectScore.

GET /v1/scanner/prospects/heat-map

Category × region matrix: aggregate readiness, demand, opportunity, and top priority per cell. Scope required: read   Cost: 0
Sort order is descending by avg_opportunity.

GET /v1/scanner/prospects/export

CSV for CRM import. Same filters as /prospects. Scope required: read   Cost: 0
Columns: domain, merchant name, category, region, readiness score, demand score, opportunity score, sales priority, and the four demand-sub-score components.

Priority thresholds

Demand score composition

  • public_intelligence — matches against the demand_intelligence data points for the merchant’s category/region.
  • synthetic_test — weighted on how often agents fail at the merchant’s checkout (more failures = more demand for an integration).
  • observatory — AI search engine mentions (ChatGPT, Perplexity, Claude) and MCP-registry listings for the domain.
  • telemetry — real agent checkout attempts observed in production traffic.