ZeqAllergy

Metabolism, nutrient modeling, meal planning.

• Protocol ID — zeq-allergy
• Category — Nutrition
• Endpoint — POST /api/nutrition/allergy
• Auth — api-key
• Rate limit — 20/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Food allergen detection and cross-contamination risk assessment. FDA Big 9 allergen scanning, alternative ingredient suggestions, restaurant safety scoring.

Signature

Request

POST /api/nutrition/allergy

Param	Type	Required	Default	Description
ingredients	array	✓	—	[{ name, source }]
allergens	array	✓	—	['peanut', 'tree-nut', 'milk', 'egg', 'wheat', 'soy', 'fish', 'shellfish', 'sesame']

Response

{ detected, crossContaminationRisk, alternatives, safetyScore, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "ingredients": [],
  "allergens": []
}' \
  "https://api.zeq.dev/api/nutrition/allergy"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/nutrition/allergy in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqAllergy alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqAllergy as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.