Scout API/developers
The same contract we consume ourselves
Scout Embed is implemented on the public API, which means the contract you get is the contract our own badge runs on. There is no richer internal endpoint, and the contracts are published and versioned.
Endpoints
- GET /v1/reports/{listing_key}
- The full scouting report, in the order the contract fixes.
- GET /v1/reports/by-url
- Identity resolution from a platform URL, returning the same object.
- GET /v1/trust-scores/{listing_key}
- The rating, the delta, the confidence band and the signal breakdown. A cheaper, lighter response for a badge or a comparison table.
- GET /v1/discovery
- A criteria search, returning ranked candidates with the coverage count alongside.
- POST /v1/watches
- A standing subscription with webhook delivery when a listing moves.
- GET /v1/registry
- Which platforms and which regions we cover, and at what access tier, so a client can know the shape of the coverage rather than guess it.
Tiers
- Developer
- Free
- 1,000 calls a month, cached reports only, attribution required.
- Growth
- £99 a month
- 50,000 calls, fresh-report requests at a per-request surcharge, webhooks included.
- Scale
- Custom
- A contracted rate limit and a support commitment.
Rate limits are per key, per minute and per month, and are returned in headers on every response. Exceeding one produces a documented 429 with a retry-after, never a silent throttle.
What every consumer of the API accepts
- Attribution to Avanti Scout, with a link to the source report, wherever a score is displayed.
- No re-selling of raw review text. It is not ours to license on.
- No use of a score to imply that Avanti Scout endorses a product. We publish an assessment of a body of reviews, which is not the same thing.
- The "as of" timestamp is passed through, so a stale score cannot be presented as a current one.
Breach terminates the key. These four exist because a score displayed without its timestamp, its attribution or its confidence band is a worse artefact than no score at all.
Contracts, published first
Every object the API returns is governed by a published, versioned JSON Schema contract: the report you get is the report the contract fixes, and the specimen report on this site validates against the same contract the product serves.
Who this is for
Price comparison sites, travel metasearch, procurement tools, consumer finance apps and journalists. If you need to show a rating that is not the platform’s own, and you need to be able to say where it came from, this is the endpoint.
A question about the API or a custom contract? Write to us