Developers

Add verify-and-refund to any recall page. One API call, or our MCP server.

First call: recalls that pay on a photo
curl "https://remedy-y0ym.onrender.com/api/v1/recalls?query=power%20bank&photo_refund=true&limit=3"

Each hit carries its proof rule: what to cut or mark, what the photo must show, and the refund. No key needed for reads; /api/health shows what is connected.

The shared hash pool

A photo already paid at one firm is held at the next, before any model call. Who may write to the pool, who may read it, and what crosses between firms:

Who may write
Firms connected to Remedy, each with a key tied to its firm (scope hash-pool:register), issued when the firm connects. Claims a firm takes on Remedy add their photo's hash as they are checked. A self-serve sandbox key can check but not register, so the pool holds only photos a firm has handled.
Who may read
Anyone, with or without a key: POST /api/v1/hash-pool/check answers whether a hash is within range of one already in the pool or a published recall picture.
What crosses
Only the 64-bit hashes and an opaque ref. No photo, no name, no contact and no firm: the registering firm is kept in Remedy's own audit ledger, never in the pool row or an answer.

Loading the recorded session

Get a free sandbox key

Playground

Every request here hits the live API. A key is optional: without one you use the demo tier of 20 requests a minute.

GET /api/v1/recalls?query=power%20bank&photo_refund=true

Search US consumer product recalls since 2024 in plain words, or list the newest that fit the filters. Each hit carries its proof rule in short.

The response appears here: status, time, request id and the full JSON.

curl "https://remedy.example/api/v1/recalls?query=power%20bank&photo_refund=true" \
  -H "Authorization: Bearer $REMEDY_KEY"

Read the docsYour keys and usageOpenAPI 3.1 spec

Source