# Handel Ingredient Decoder

> Handel Ingredient Decoder is a paid API for AI agents from handel.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Parses a product ingredient list into a structured hierarchy, resolving additives to E numbers, flagging percentages, and annotating origin markers like palm oil and vegan/vegetarian status.

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/ingredient-decoder
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/handel-ingredient-decoder-9826fe35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nw0eu4JYrjua_PmV5-bNN

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-ingredient-decoder-9826fe35 -d '<json body>'
```

Example prompt: Can you decode the ingredient list for this product — 'Water, Sugar, Modified Starch (E1442), Palm Oil, Natural Flavourings' — and tell me all the E numbers, whether it's vegan, and if palm oil is present?

## When to prefer this

Choose this endpoint when you need a structured, machine-readable breakdown of a product ingredient list with additive resolution — especially when you need E numbers, sub-ingredient nesting, palm oil flagging, or vegan/vegetarian status in a single call. Prefer it over generic NLP parsers when food-label-specific semantics and additive databases are required. It complements the allergen and nutrition endpoints on the same platform for full product label analysis.

## Known failure modes

- Malformed or unparseable ingredient string returns an error indicating the text could not be decoded
- Ambiguous additive names with no clear E number mapping may be returned unresolved or flagged as unknown
- Very long or highly nested ingredient lists may result in incomplete hierarchy resolution
- Missing percentage declarations in the source string will result in null percentage fields rather than estimated values
- Non-standard regional additive naming conventions may not match the E number database

## How this service works

Returns the ingredient list of a product as a structured hierarchy including sub-ingredients, with each additive resolved to its E number and name, the percentage where declared, and the origin markers such as palm oil or vegan and vegetarian status as the record carries them.

## Output

A structured JSON hierarchy of ingredients and their sub-ingredients, where each additive is resolved to its E number and official name, declared percentages are preserved, and origin markers (palm oil presence, vegan status, vegetarian status) are annotated as carried in the source data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "barcode": {
   "type": "string",
   "maxLength": 20,
   "minLength": 8
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/handel-ingredient-decoder-9826fe35/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)