Provenance model · every value should explain where it came from

RecallRadar is built for teams that need to inspect source context before they automate around a record. The API, MCP tools, and snapshots carry source identifiers, source URLs, and field-level notes. Sources move and retire pages, so exactly what each claim lets you verify is laid out in what you can verify.

Provenance is evidence context, not a warranty. Source terms, update cadence, and coverage limits still apply; review /docs/sources for source and licence notes, and /docs/data-dictionary for the full field catalog.

What provenance means here

Each exported record under /v1/recalls can combine values from multiple upstream records. Provenance records keep those values auditable by naming the field, source, source class, source record URL, and whether the value is currently effective.

What you can verify

Public claims come in three tiers, and each tier says exactly what it lets you check. Nothing on this page asks you to take a link on faith.

1. Source ownership — always verifiable

Every provenance record names the source and source class behind the value. That attribution is part of the delivered record itself and does not depend on any external page staying up.

2. Release receipts — always verifiable

The release version and snapshot fingerprint tie everything you receive to one exact, immutable delivery. If a question comes up later, the receipt identifies the data you evaluated, whatever the live web does.

3. Resolvable evidence routes — checked every release

Provenance also keeps each record URL exactly as the source published it. Public sources move and retire pages, so rather than implying every deep link resolves, a bounded sample is probed each release and the result is stated below. A field whose sampled link does not resolve is displayed as UNVERIFIED rather than as resolved; resolving ones are displayed as resolved only while the check says so.

Link check 2026-09-16: 46 of 48 sampled evidence links resolved (2 unavailable). Deep links are working pointers as of this release.

source_record_url / field-level provenance shapejson

{
  "field": "field_name",
  "source": "accc",
  "source_class": "government | registry | manufacturer | aggregator | derived",
  "source_record_url": "https://www.productsafety.gov.au",
  "effective": true,
  "superseded_at": null
}

How to inspect it

Start with a narrow API call, inspect the nested provenance payload, then compare source codes against the source registry. Snapshots preserve the same model in export-friendly tables and ship licence notes alongside the data files.

provenance inspectionbash

curl -s "https://api.recallradar.dev/v1/recalls?q=Galmet%20ColdGal%20Brushable%20Paint&is_recall=true&limit=5" \
  -H "Authorization: Bearer $RECALLRADAR_API_KEY"

curl -s "https://api.recallradar.dev/v1/sources" \
  -H "Authorization: Bearer $RECALLRADAR_API_KEY"

The manifest example Search strict recalls starts at /v1/recalls?q=Galmet%20ColdGal%20Brushable%20Paint&is_recall=true&limit=5: Search authenticated production access for strict recall records.

Fields with source context

These field catalog entries are the fields most likely to carry provenance notes or audit-specific scope. The complete list is in the data dictionary.

authorityNotice identity

Source authority code, such as cpsc, eu-safety-gate, health-canada, gov-uk-opss, accc, fr-rappelconso, tw-bsmi, or fi-tukes-historical.

Provenance: Mapped directly from the source connector and source registry code.

idNotice identity

Unique numeric notice identifier within RecallRadar.

Provenance: Generated by the notice ingestion spine and stable within the published snapshot.

source_notice_refNotice identity

Authority-specific reference number or ID, such as a CPSC recall number or RAPEX alert ID.

Provenance: Copied from the original notice identifier when the authority publishes one.

is_recallRecall classification

True when the notice is a formal recall; false for alerts or warnings that stop short of recall.

Provenance: Derived from authority notice type and source-specific recall/alert labels.

source_record_urlProvenance

Canonical URL of the original notice on the authority website.

Provenance: Copied from the source notice URL used for audit and citation.

_provenanceProvenance

Per-field provenance map with source, confidence, fetched timestamp, and source URL.

Source catalog

Source descriptions explain coverage and redistribution posture before a buyer opens the full source table.

ACCC Product Safety

Commercial-use cleared

ACCC Product Safety Australia recall notices under Creative Commons Attribution 4.0.

CPSC

Commercial-use cleared

US Consumer Product Safety Commission recall records and public-domain safety notices.

EU Safety Gate

Commercial-use cleared

EU Safety Gate and RAPEX product-safety alerts under the European Commission legal notice and reuse terms.

France RappelConso

Commercial-use cleared

French national consumer-product recall notices under Etalab Licence Ouverte 2.0, with source and update-date attribution.

Reviewer caveats

Review these limitations alongside the field and source notes before production use.

RecallRadar is reference data, not legal advice, product-safety certification, or recall-management advice.
Buyers remain responsible for validating source notices and regulatory obligations in their own jurisdiction.
The dataset covers selected consumer-product authorities and excludes food, drug, vehicle, agriculture, and unlisted global sources.

Related evaluation guides

Connect this diligence evidence to the relevant integration decision.

Product Safety Notice API