# Handel Reformulation Detector

> Handel Reformulation Detector is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-15).

Monitors a food product over time by storing a snapshot on first call and reporting ingredient, allergen, additive, nutritional, and packaging changes on subsequent calls.

## Facts

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

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 handel-reformulation-detector-0e9a4c11 -d '<json body>'
```

Example prompt: Keep an eye on Nutella — barcode 3017620422003 — and let me know if the ingredient list, allergens, or nutritional values have changed since the last time you checked.

## When to prefer this

Choose this endpoint when you need to track food product reformulations over time — specifically to detect changes in ingredients, allergens, additives, nutrition, or packaging between calls. It is purpose-built for repeat monitoring with memory, unlike a single-call barcode lookup or allergen check. Prefer it over static product lookup endpoints when continuity and change detection across time are the goal.

## Known failure modes

- Product barcode not found in Open Food Facts or product database — returns error with no snapshot stored
- First call always returns a 'snapshot stored' acknowledgment rather than a diff — agents expecting immediate comparison on first call will receive no change data
- Network timeout when upstream product database is slow
- If the product data source has not updated since last snapshot, no changes will be reported even if a reformulation occurred
- Invalid or malformed barcode input returns a validation error

## How this service works

A monitor with memory over food products. The first call stores a snapshot and says so rather than reporting everything as new. Later calls compare and report differences in the ingredient text, the allergen and trace lists, the additives, the nutritional values, the quantity, the serving size and the packaging.

## Output

On the first call the endpoint stores a product snapshot and returns a confirmation that the baseline has been saved rather than flagging everything as new. On subsequent calls it returns a structured diff covering: changed or added/removed ingredients and sub-ingredients, allergen and trace warning changes, additive changes, nutritional value differences per 100g, quantity and serving size changes, and packaging changes. Items that are unchanged are not reported.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "barcodes": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 20,
    "minLength": 8
   },
   "maxItems": 25,
   "minItems": 1
  },
  "snapshot_token": {
   "type": "string",
   "maxLength": 80
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/handel-reformulation-detector-0e9a4c11/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)