# HALOWERK Recall Check

> HALOWERK Recall Check is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Checks a food product for active recalls or safety alerts, returning structured recall status information.

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/recall-check
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-recall-check-09ae90a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AKhzW7Mdg8R7v2a1YBz_P

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-recall-check-09ae90a0 -d '<json body>'
```

Example prompt: Can you check if this product — barcode 4005808002788 — has any active recalls or safety alerts I should know about before I put it on the shelf?

## When to prefer this

Choose this endpoint when you need a quick, paid, structured recall-status lookup for food products — especially in retail, import/export, or consumer safety workflows where you need a definitive yes/no on active recalls rather than manual searching of government recall portals. Best suited for agents processing individual product checks at point of purchase, intake, or listing.

## Known failure modes

- Product not found in recall databases — returns no-match or unknown status
- Invalid or malformed barcode input causing a 400-level error
- Recall database temporarily unavailable causing a timeout or 503 error
- Payment failure via x402 preventing endpoint access
- Product found but recall data is ambiguous or outdated

## How this service works

HALOWERK handelswerk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

Returns structured information about whether the product is subject to any active recalls, safety withdrawals, or official alerts, including details such as recall reason, affected batches, issuing authority, and current status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "gtin": {
   "type": "string",
   "maxLength": 20,
   "description": "Barcode / GTIN / EAN, digits only."
  },
  "brand": {
   "type": "string",
   "maxLength": 120,
   "description": "Brand or manufacturer name."
  },
  "limit": {
   "type": "integer",
   "default": 20,
   "maximum": 50,
   "minimum": 1
  },
  "since": {
   "type": "string",
   "maxLength": 10,
   "description": "Only alerts published on or after this date, YYYY-MM-DD."
  },
  "product": {
   "type": "string",
   "maxLength": 200,
   "description": "Product name or free-text description."
  },
  "category": {
   "type": "string",
   "maxLength": 80,
   "description": "Safety Gate category, e.g. \"Toys\", \"Cosmetics\"."
  },
  "risk_level": {
   "enum": [
    "any",
    "serious"
   ],
   "type": "string",
   "default": "any"
  },
  "country_of_origin": {
   "type": "string",
   "maxLength": 60,
   "description": "Country of origin as named in the alerts, e.g. \"China\"."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-recall-check-09ae90a0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from handel.halowerk.com](https://www.zero.xyz/host/handel.halowerk.com/llms.txt)