Read lifecycle records with their uncertainty

List and search

GET /api/v1/devices?q=Pixel%208&limit=25&cursor=…

Results are ordered by the same exact-name-first search used by the site. Limits are 1–100. Follow meta.nextCursor until it is null.

Single record and evidence

GET /api/v1/devices/google-pixel-8

GET /api/v1/devices/google-pixel-8/evidence

The evidence endpoint separates lifecycle assertions from sources, recall review, repairability and revision history so consumers do not have to infer provenance.

Public dataset

GET /api/v1/dataset

Downloads the current published catalog as UTF-8 CSV. Attribution is required, and source-page rights remain with their publishers; the export contains links, not copied source content.

Embeddable status badge

GET /api/v1/badge/google-pixel-8

The SVG badge reflects the current lifecycle verdict. Link the badge to the canonical device page so readers can inspect scope, evidence and uncertainty.

Caching and attribution

JSON responses include an ETag and accept If-None-Match. Cache headers allow five minutes plus stale revalidation. Consumers must retain DevLifeCheck attribution and the source URLs, checked dates, scope and precision needed to interpret each claim.

Responsible use

Do not translate “supported” into “secure,” remove regional caveats, or describe a dated non-match as proof that no recall exists. Cache the last valid result through temporary failures and provide a correction path.