$0.05 / check
Whether a matching enforcement record exists — and what that does not mean.
Connect enforcement_check to your agentWhat it answers
Search published enforcement actions by barcode, product, or firm. Read the limits before relying on it: the agency publishes no structured barcode on any record, so a barcode search works by extracting one from a free-text code field that only a minority of records carry — and finding nothing is therefore not evidence that a product is unaffected. Status reflects the record as published at classification and the agency does not update it afterwards. This answers whether a matching record exists; it does not answer whether a product is safe.
Ask it things like
- Is there an enforcement record naming this barcode?
- What has this firm recalled this year?
- Which actions mention this product description?
What comes back
A receipt, and the same envelope on every tool — so a caller writes against one contract whichever one they call. The citations carry two clocks that are never collapsed: citature's retrieved_at and the source's own as_of, plus the record's own published_at and record_version where the source publishes them.
Answer
citature — enforcement_check receipt
- answer
- The rows themselves, typed per tool. Amounts carry their unit and their basis, because a figure per serving and one per 100 g are not comparable.
- citations
- The record behind the answer: a re-runnable upstream URL, citature's retrieval clock, the release's own currency date, and the record's own version.
- coverage
- What this answer does not reach, and where the record is silent rather than negative.
- guardrails
- The standing caveats, shipped in the answer itself rather than only on a page an agent never loads.
- matches
- Every join the answer used, named by method and confidence. A name match is reported as a name match, never as an identity.
- schema_version
- The conformed schema the answer was produced against, so a caller can pin it.
What this figure is
Input
| param | type | required | notes |
|---|---|---|---|
| gtin | string | no | Barcode, best-effort text match. |
| product | string | no | Product description. |
| firm | string | no | Recalling firm. |
| since | date | no | Reported on or after YYYY-MM-DD. |
| limit | integer 1–500 | no | Max rows; default 50. |
Sources
Primary federal records only, never an aggregator. This answer's citations name:
- openfda
Pricing
$0.05 / check — metered per served answer. The answer is produced first and the meter is touched only once it is in hand, so a call that returned nothing is never billed.
Connect enforcement_check to your agentguardrails & coverage
- Research over public records and product labels — not medical, nutritional, or safety advice.
- citature reports what the record says. It never renders a verdict, a pass/fail, a diagnosis, or a recommendation, and is not a substitute for a clinician.
- Answers are product-, substance- or population-level only — foods, supplements, labels, substances, enforcement actions, and dietary intake as a weighted survey estimate. No answer returns or describes an individual person, and citature links no record to individually identifiable data.
- A record that does not declare something is not a record declaring its absence. citature reports what a record states; it cannot report what a product does not contain, or what a population did not consume.
- A Daily Value is a labelling reference from federal regulation, not a Dietary Reference Intake. citature carries no licensed source for Dietary Reference Intakes and does not estimate whether anyone meets a nutrient requirement.
- Coverage reflects the records citature has ingested, not the full upstream history. Each dataset advances when its source publishes a release.
- Every answer states its own coverage caveats in the receipt's `coverage` field, alongside these standing guardrails.