API

Two ways to query, both CORS-enabled and read-only. All data is regenerated from the monthly FIDO MDS blob and the community provider list.

1 · REST API (paginated)

GET /api/v1/authenticatorsPaginated list
GET /api/v1/authenticators/{id}Full entry by AAGUID / AAID / key id
GET /api/v1/metaBlob number, next update, counts

Query parameters for the list endpoint

searchFuzzy match on name or AAGUID
pagePage number, default 1
per_pageItems per page, default 20, max 100
sourcecommunity (passkey providers) or mds (FIDO devices)
typefido2, u2f, or uaf
statusFIDO_CERTIFIED or NOT_FIDO_CERTIFIED

Examples


    

Response fields (every entry, list and detail alike)

idAlways present. The AAGUID for FIDO2 and passkey providers; the attestation certificate key id for U2F; the AAID for UAF.
nameAlways present. Curated display name (community name preferred, else the MDS friendly name).
iconAlways present. Path to a static image under data/, e.g. icons/{id}.png. null only when the vendor never published an icon (4 of 557 entries).
iconDarkDark-theme icon path; non-null for community-sourced providers.
type, source, status, timeOfLastStatusChangeProtocol family, data source (mds / community / both), latest certification status (null for community-only entries), and its date.

Detail responses for MDS entries additionally nest the raw metadataStatement and statusReports from the blob, unmodified except that icons are extracted to files.

2 · Static files (works on any static host)

data/index.jsonEvery authenticator: id, name, type, source, status, icon paths
data/entries/{id}.jsonFull metadata for one authenticator
data/icons/{id}.png|svgIcon (community providers: {id}-light.svg / {id}-dark.svg)
data/meta.jsonBlob metadata and counts

Response entries carry a source field: mds (FIDO Alliance MDS), community (passkey provider list), or both (merged).