Data Quality

Ihr API-Schlüssel. Authorization: Bearer <key> wird ebenfalls akzeptiert.

The response payload.

Per-field completeness across the firearms table.

Total records matching the query across every page.

Per-field completeness, keyed by column name.

Per-field completeness across the calibers table.

Total records matching the query across every page.

Per-field completeness, keyed by column name.

Per-field completeness across the manufacturers table.

Total records matching the query across every page.

Per-field completeness, keyed by column name.

Optional. Ohne Schlüssel antwortet dieser Endpunkt nach der öffentlichen Richtlinie; ein Schlüssel erhöht Ihre Limits und schaltet planabhängige Felder frei. Authorization: Bearer <key> wird ebenfalls akzeptiert.

Report on one catalog instead of all of them. Every check is a scan of a catalog table, so a scoped call runs only the checks that concern that catalog and is the cheaper request by a wide margin. Omitted, the whole report comes back.

Akzeptiert

manufacturersfirearmscalibersattachmentsammunition

The response payload.

Which catalog this report covers, or all. Echoed so a stored copy still says what it describes.

Two different times, deliberately separate. The gap report is recomputed on every request, so computedAt describes this body. The daily snapshot is what has a last run and a next run, and it is what /v1/data/gaps/history records.

When this response was computed. Not when you read it: the response is edge-cached for a minute, so a body can be up to that old.

How often the recorded snapshot is taken.

When the last snapshot was stored, or null before the job has ever run.

The UTC day that snapshot describes.

When the next snapshot is due.

When the daily source audit last judged the catalog's citations, or null before it has ever run. Its own time rather than the snapshot's: record-cites-an-authority reads a table a separate job writes, and the two run in parallel.

Keyed by entity. Each carries its total and, per tracked field, how many records lack it. A field is missing when it is null or empty, so a column full of empty strings does not read as complete.

Visual coverage, one entry per catalog that stores media - firearms today, and an empty array for a scope that stores none. A catalog with no pictures and a catalog that does not hold pictures are different answers, so absence is never reported as zero coverage. Each kind is counted twice: records is how many records have at least one asset of that kind, which is the coverage figure, and assets is how many files exist, which is larger wherever a record carries several. none is how many records have nothing to show at all. This is what field coverage cannot report. A firearm's line drawing is a column, but its photographs, renders and 3D models are rows in a media table, so "does this record have a render" is not a question a field count can answer.

Which catalog this covers.

How many records that catalog holds.

Keyed by kind: silhouette, photo, render, model, schematic. Each carries records, assets and coveragePct.

Records with no drawing, photograph, render, model or schematic.

One entry per integrity check, each naming what passing means so a failure is actionable without reading the source.

Stable id, usable at /v1/data/gaps/checks/{checkId}.

What passing means.

Production status, one of in_production, discontinued, out_of_production, in_service, limited_production, prototype. Discontinued records are kept deliberately: a rifle built in 2004 wears parts nobody sells today.

How many records failed.

Up to five failing ids. Ask the check endpoint for the rest.

The distinct values behind the failure, present only on a check about a value rather than a record. A vocabulary failure is decided once per spelling rather than once per record, so thirty-four records reporting nineteen spellings are nineteen decisions, and ids alone would mean fetching thirty-four records to recover them. Absent on every other check rather than empty, so a check with no values to report and a check that found none cannot be confused.

Reserved for whether each cited website still resolves, which a scheduled job will fill. Reports unavailable with a reason until then.

Optional. Ohne Schlüssel antwortet dieser Endpunkt nach der öffentlichen Richtlinie; ein Schlüssel erhöht Ihre Limits und schaltet planabhängige Felder frei. Authorization: Bearer <key> wird ebenfalls akzeptiert.

Only tasks in this state.

Akzeptiert

openclaimedin_progressresolvedunverifiablenot_a_fault

Only tasks for one catalog.

Akzeptiert

manufacturersfirearmscalibersattachmentsammunition

How many to return.

Bereich

1 – 200

Beispiel

50

The response payload.

Most recently seen first.

Stable id, derived from the finding rather than assigned, so the same finding is the same task tomorrow.

What the asset is: silhouette, render, photo, schematic, model. /v1/firearms/{id}/media/{selector} addresses an asset by this.

Which catalog.

The record, or for a vocabulary task the value being decided.

The check id or field this came from.

Production status, one of in_production, discontinued, out_of_production, in_service, limited_production, prototype. Discontinued records are kept deliberately: a rifle built in 2004 wears parts nobody sells today.

How many records this would fix. One for most; a vocabulary decision covers every record holding that spelling.

When the finding was first seen.

When a worker began, or null.

When it closed, or null.

Whether a worker has filed a conclusion. Never what it says.

Optional. Ohne Schlüssel antwortet dieser Endpunkt nach der öffentlichen Richtlinie; ein Schlüssel erhöht Ihre Limits und schaltet planabhängige Felder frei. Authorization: Bearer <key> wird ebenfalls akzeptiert.

The task id, as the list reports it.

Beispiel

gap:firearms.year_introduced:anschutz-1913-super-match

The response payload.

The task, in the public shape the list returns.

Optional. Ohne Schlüssel antwortet dieser Endpunkt nach der öffentlichen Richtlinie; ein Schlüssel erhöht Ihre Limits und schaltet planabhängige Felder frei. Authorization: Bearer <key> wird ebenfalls akzeptiert.

How many days back to read. One row per day, so 90 is a quarter.

Bereich

1 – 365

Beispiel

90

The response payload.

The window that was read.

One row per day, oldest first.

The UTC day this row describes.

When the snapshot was taken.

Which catalog the run covered.

How many integrity checks ran.

How many of them failed.

How many records were behind those failures, summed across checks.

Weighted field coverage across every tracked catalog, as a percentage of possible values. Null before any field is tracked.

Ihr API-Schlüssel. Authorization: Bearer <key> wird ebenfalls akzeptiert.

Which catalog to report on

Akzeptiert

manufacturersfirearmscalibersattachmentsammunition

Beispiel

manufacturers

The field the records are missing. Which fields are valid depends on entity, since each catalog tracks different columns: a field the named entity does not track is refused with 400 and the error lists the ones it does.

Beispiel

website

Page number, from 1 to 10,000

Bereich

1 – 10000

Beispiel

1

Items per page (max 100)

Bereich

1 – 100

Beispiel

20

One page of results

Slug of the record.

Its name, so a worklist is readable without a second lookup.

The field this row is missing. Echoed so a stored batch still says what it was collected for.

What the record holds in that field. Always null here: the query selects records missing it, so this says "no value" rather than "not looked at".

The pages the record already cites. Carried so a consumer can judge whether the missing value is findable without fetching the record first.

Current page number

Items per page

Total matching records (Builder and above)

Ihr API-Schlüssel. Authorization: Bearer <key> wird ebenfalls akzeptiert.

The check id, as /v1/data/gaps reports it.

Beispiel

firearm-manufacturer-exists

The response payload.

The check.

What passing means.

Every failing record.

Ihr API-Schlüssel. Authorization: Bearer <key> wird ebenfalls akzeptiert.

Only return records scoring below this threshold

Bereich

0 – 1

Beispiel

0.5

Page number, from 1 to 10,000

Bereich

1 – 10000

Beispiel

1

Items per page (max 100)

Bereich

1 – 100

Beispiel

20

One page of results

Slug of the firearm.

Display name, as the maker writes it.

How completely the record is specified and how well it is sourced, 0 to 1. A record-level completeness and provenance measure, not a per-field probability of correctness. dataConfidence on the camelCase endpoints.

Current page number

Items per page

Total matching records (Builder and above)