Skip to main content
GET
Check evidence coverage

Authorizations

X-API-Key
string
header
required

Team-scoped API key created in the app (Settings → API Keys). Sent as X-API-Key: <key> on every request. The header name apikey is also accepted as an alias.

Query Parameters

product_id
string<uuid>

Filter by one product ID from /products.

product_feature_id
string<uuid>

Filter by one buildable product feature ID from /features.

product_area_id
string<uuid>

Filter by one parent product-area ID from /areas.

feature_area_id
string<uuid>

Filter by one child feature-area ID from /areas. A feature area is the subject area an insight is filed under; it is NOT a buildable feature ID from /features, and the two are never interchangeable.

date_from
string<date>

Inclusive start date, as a real calendar date in YYYY-MM-DD. Any other form is rejected with 400 VALIDATION_ERROR - including 2026-5-1, 2026/05/01, May 1, 2026, a bare 2026, a date-time, and impossible dates such as 2026-02-30.

Pattern: ^\d{4}-\d{2}-\d{2}$
date_to
string<date>

Inclusive end date, as a real calendar date in YYYY-MM-DD. Validated by the same rule as date_from.

Pattern: ^\d{4}-\d{2}-\d{2}$

Response

Coverage verdict and supporting totals

verdict
enum<string>
required

Whether absence or weak evidence in the requested scope can be interpreted meaningfully.

Available options:
informative,
too_thin,
pre_coverage
reason
enum<string>
required
Available options:
no_team_feedback,
window_before_team_coverage,
empty_scope_window,
below_density_threshold,
density_threshold_met
reads_as
string
required

Human-readable interpretation of the verdict.

policy_version
string
required
Example:

"1"

density_threshold
integer
required
Example:

50

filters
object
required
date_range
object
required
scope
object
required
team
object
required