Finds the allergen your menu declares and your recipe contradicts
Allergen information is a legal requirement, it changes whenever a supplier changes a recipe, and it is maintained by whoever has time. The failure is not a fine. It is someone in hospital.
This agent does the documentary work. It cross-checks the allergens each dish declares against the ingredients it actually contains and the specifications your suppliers provided, and reports every mismatch: an allergen present and undeclared, one declared but not evidenced, a supplier spec that changed while the menu did not, an ingredient with no specification at all.
It never tells anyone a dish is safe. Not for a customer, not for a category of customer, not in general. Cross-contamination depends on a kitchen it cannot see, and a reassurance is the only output here that could seriously hurt somebody. It reports discrepancies to the person responsible for the menu, who decides.
Before a customer relies on the menu.
What was checked, against which specifications, and when.
Re-run it whenever a recipe or a supplier changes.
Every dish's declared allergens checked against what its ingredients actually contain.
The allergen in the stock, in the sauce, in the dish. This is where undeclared allergens hide.
A supplier reformulated and the menu never changed. Nobody catches this manually.
An ingredient nobody has a spec for is an unknown, and it is reported as one.
An allergen the recipe contains and one nothing rules out are different findings.
No dish is described as safe or suitable for anyone. Cross-contamination depends on a kitchen it cannot see.
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
Demo dataIllustrative sample output, abridged.
{
"dishes": [
{
"name": "Tomato soup",
"declaredAllergens": [
"celery"
]
}
],
"market": "EU"
}{
"escalate": true,
"findings": [
{
"dish": "Tomato soup",
"issue": "present-undeclared",
"foundIn": "Vegetable stock base — supplier specification lists skimmed milk powder.",
"allergen": "milk",
"sourceDocument": "Stock Base 4kg — supplier spec, 2026-05-11"
}
],
"disclaimer": "A comparison of your records against each other. Cross-contamination, shared equipment and kitchen handling have not been assessed, and nothing here states that any dish is safe for any person.",
"escalationReason": "Milk is present in Tomato soup via the stock base and is not declared.",
"allergenListSource": "Supplied EU 14-allergen list",
"ingredientsWithoutSpecification": [
"House herb blend — no supplier specification on file."
]
}No integrations required.
Check every affected dish before printing.
Find which dishes are now wrong.
Find the gaps in your own records first.
$149/month
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits.
No, and it must never be used that way. It compares your records against each other. Whether a dish is safe for a particular person depends on their condition and on your kitchen, and that answer must come from a responsible person.
No. Cross-contamination is a matter of kitchen practice, shared equipment and storage — none of which is in a recipe. It reports what your documents say and says explicitly that it has not assessed handling.
It works from the allergen list for your market, supplied or loaded. Lists differ by country and change, and an agent quoting a remembered list would be quoting the wrong one.
No reviews yet. Reviews open once customers have run this agent.
Tell us what to change and our team will scope a customised version for your business.
Customize this agent