# Handel Allergen Check

> Handel Allergen Check 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).

Returns allergen declarations, trace warnings, ingredients text, and record completeness for a food product identified by barcode, explicitly distinguishing 'not declared' from 'not present'.

## Facts

- Endpoint: POST https://handel.halowerk.com/v1/allergen-check
- 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-allergen-check-ce1cc5f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xk_4u7noru7vU0u_K9wwy

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-allergen-check-ce1cc5f2 -d '<json body>'
```

Example prompt: Can you check the allergen declarations for the product with barcode 5000118491121 — I need to know what allergens are listed, any trace warnings, and whether the record is complete or if some fields were never filled in?

## When to prefer this

Choose this endpoint when you specifically need allergen safety data — including the critical 'not declared vs not present' distinction — for a packaged food product identified by barcode. It is the right choice for allergy screening, compliance checks, and label auditing where a false negative (empty field misread as safe) would be dangerous. Prefer this over a general barcode lookup when allergen detail and record completeness are the primary concern rather than just product name or nutrition values.

## Known failure modes

- Barcode not found in Open Food Facts or product database — returns empty or null allergen fields with a not-found indicator
- Allergen fields never submitted by volunteers or manufacturer — returned as 'not declared' rather than 'not present', which may be misread as safe
- Ingredients text available only in a language the caller doesn't expect
- Incomplete record with partial allergen data — completeness score is low but some fields are populated
- Invalid or malformed barcode input — likely returns a validation error or empty result

## How this service works

Returns what a product declares about allergens: the allergen tags, the trace warnings, the ingredients text in its original language, and the completeness of the record. The distinction it holds to throughout is between not declared and not present. The data come from volunteers and manufacturer submissions, so an empty allergen field means nobody entered one, and for somebody with an allergy that difference is the difference that matters — every absent allergen is therefore reported as not…

## Output

A structured response containing: declared allergen tags (e.g. gluten, milk, nuts), trace/may-contain warnings, the original-language ingredients text, and a completeness indicator for the record — with explicit flags distinguishing allergens that are 'not declared' (field was never submitted) from those confirmed 'not present'.

## 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-allergen-check-ce1cc5f2/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)