THE HARNESS, AS AN API
An AI recipe, re-read before it is served.
Send any recipe, written by your model or ours. The harness runs it through eight checks, marks the line that does not hold, and refuses what breaks an allergy. Even corrected. The food graph and the ingredient cast — 680 3D toys, 678 drawings — come through the same key.
500 calls a month, no card. Then per call, in Canadian dollars.
curl https://api.rikaido.app/v1/harness/validate \
-H "Authorization: Bearer rk_live_…" \
-d '{
"recipe": {
"title": "Chicken satay",
"ingredients": [
{ "name": "chicken thigh", "quantity": "600", "unit": "g" },
{ "name": "peanut butter", "quantity": "80", "unit": "g" },
{ "name": "salt", "quantity": "1", "unit": "tsp" }
],
"steps": [
{ "instruction": "Sear until deeply golden.", "tempC": 200 }
]
},
"constraints": { "allergies": ["peanut"] }
}'THE ANSWER
The line that does not hold is marked. The rest is served.
Every code in the answer names a check. “safe” is the one lock: a recipe that breaks an allergy is never served, even after correction. “ok” is an opinion, not a refusal.
WHAT IS CHECKED
Eight checks. Twenty codes. One lock.
The validator is pure: no model, no network, the same answer twice. The specification and the schemas are published; the verified recipe base and the cooking bands stay ours. Read the specification →
- 01Safetyallergies, diets, exclusions
- 02Dishcategory, baked or not
- 03Structureenough steps, enough ingredients
- 04Quantitiesmeasured, never vague
- 05Saltwithin the dish’s band
- 06Doughleavening, hydration, yeast
- 07Temperaturesplausible, within the band
- 08Techniquesnamed, recognised, at their temperature
THE PRICE
Per call. Nothing else.
500 calls a month to build with, no card. Then every call is counted and billed once a month by Stripe, in Canadian dollars. No subscription, no tiers.