For professionals

Reverse-engineer the flavor. Then rebuild it.

The same engine that helps someone bring back a grandmother's dish, for the people who rebuild flavor for a living. Achiote takes a dish or a drink — one you tasted, one you're developing, or one you need to change — and reformulates it under real constraints: cost, sourcing, ABV, allergen, dietary, what's in season. It reasons over the food science and shows its work, instead of guessing a recipe.

The workflow

From a problem to a spec

Same engine as the rest of Achiote, pointed at the pass and the bar. It investigates before it answers, and keeps the evidence honest.

Describe

The dish or drink, the target, or the constraint you're working against.

Reason

Food science: browning, fermentation, acid, fat, bitterness, dilution, aroma.

Reformulate

Substitutions solved against cost, sourcing, ABV, allergen, or season.

Spec

A build you can run or pour, with the unknowns kept visible.

Four jobs it does today

From a problem at the pass or the bar to a spec

Reverse-engineer · dish

The dish you tasted somewhere

"I had a dark, complex mole on a trip — deep, a little sweet, smoky, layered. I want a version for my menu."

MechanismSeparates what you said (dark, sweet, smoky, layered) from what's inferred — a chile base, a toasting step, a fat-and-acid balance that carries the depth. ReformulateProposes a candidate build with sourcing for the harder ingredients and accessible substitutes where exact ones are regional. First testConfirm the toasted-chile aroma before scaling the full sauce.

Zero-proof · drink

A Negroni that still bites — without the alcohol

"Make a zero-proof Negroni that actually tastes like a Negroni, not sweet juice."

MechanismThe signature is bitter (Campari's quinine-class bitterness) against botanical gin and sweet vermouth, carried by ethanol's heat and dilution. ReformulateA bittering agent for Campari's backbone, a zero-proof botanical base for the gin lift, and verjus or salt to restore the grip the tongue expects. First testBuild the bitter-to-sweet ratio first — that balance is the whole drink.

Cost / availability · either

The ingredient that tripled in price

"My hero dish or build leans on an ingredient that's over budget or out of season. What holds it together?"

MechanismIdentifies the ingredient's actual role — the browning, the acid, the fat, the bitterness, or the texture it contributes. ReformulateRanks substitutes by flavor-and-function overlap and cost, flagging where a swap shifts seasoning or texture and how to correct it. First testMatch the dominant role first; adjust to hold the original impression.

Allergen / dietary · dish

Gluten-free, nut-free, or vegan — without losing the dish

"I need a version of this dish without dairy and without gluten that still tastes like the original."

MechanismPinpoints what the removed ingredient was doing — emulsification, body, browning, or binding — so the swap restores the function, not just the label. ReformulateProposes constraint-respecting substitutes and flags what changes, so you adjust deliberately. First testTaste the restored function before plating. Verify every allergen claim independently — this is not allergy or medical advice.

Illustrative flows. Achiote reasons from food-and-drink science and separates evidence from inference; it does not claim a single "correct" recipe. Not medical, allergy, or nutritional advice — verify any substitution before serving.

Who it's for

Built for the people developing food & drink

Chefs & menu developers

Develop and adapt dishes faster. Reverse-engineer an inspiration, solve substitutions against your cost and supply reality, keep a spec with the reasoning attached.

Beverage & cocktail developers

Build and rebuild drinks — zero-proof, lower-ABV, cost- or supply-constrained — with the flavor science behind each call, integrable via the API.

Menu & reformulation consultants

Produce more specs in less time across clients. Constraint-aware reformulation — cost-down, seasonal, allergen-safe — handed over as a build sheet.

Reach it where you work

One engine, four ways in

Web app

Try any flow now, no setup. Open the app →

API

Integrate reconstruction into your own tool. POST /v1/ask with an API key. Contract →

MCP / CLI

Drive it from an AI agent or the terminal: reconstruct_food_memory or achiote ask.

It's the same Achiote. The engine a chef trusts to rebuild a dish under constraints is the one that brings back a family recipe nobody wrote down. Cooking from a memory, not a menu? Start here →