foodoracle.engine
01 // Data_Model
Four modular capability areas — you only pay for what you use.
02 // Interface
03 // Security_Protocol
Transport encryption (HTTPS) for every request.
Four modules. One data foundation.
Book only what you need — each module solves a concrete problem around ingredients, health, cooking and nutrition.
Find and normalize any ingredient — across languages.
- Multilingual search (keyword + semantic)
- Typo-tolerant autocomplete
- Full ingredient profiles with stable IDs
- Categories, units & languages as master data
Is this safe for this diet?
- Allergens & intolerances across 14 domains
- Diet check: vegan, vegetarian, pescetarian, pork-free
- FODMAP incl. safe portion sizes
- Histamine incl. DAO effect & thresholds
What pairs with it — and what can I use instead?
- Substitutes with quality score (food graph)
- Flavor pairings & common co-use
- Similar ingredients (family + functional)
- Per-ingredient unit conversion
What's inside — per ingredient and per serving?
- Nutrition per ingredient (per 100 g)
- Recipe analysis: nutrition per serving
- Macros & energy in detail
- A base for fitness & nutrition features
Deterministic. No LLM.
Same request, same response — reproducible, explainable, in milliseconds. Curated data, not guesses.
Reproducible
Same input → same output. Every time.
Explainable
Traceable results from curated data — no black box.
Fast
Responses in milliseconds, not seconds.
No hallucinations
No invented quantities or combinations.
Protocol_Documentation
Speak the language of the engine.
Exchange rates.
(Save 20% on annual)
Free
No credit card required
≈ 1,000 searches or 200 compatibility checks per month
-
All modules (M1–M4)
-
For evaluation & prototypes
-
Community support
Pro
then €0.001 / Credit
≈ 25,000 searches or 5,000 compatibility checks per month
-
All modules (M1–M4)
-
Commercial use
-
Spending limit on by default
-
Email support
Scale
then €0.001 / Credit
≈ 250,000 searches or 50,000 compatibility checks per month
-
Everything in Pro
-
Priority support
-
Highest rate limit
Enterprise.
SLA & dedicated support · Own index / bring your own data · On-prem option
How credits work.
Every API call costs credits — weighted by module. What you don't use costs nothing.
Example: 1 ingredient search (M1) = 1 credit · 1 compatibility check (M2) = 5 credits.
Your spending limit.
Every new subscription starts with a spending limit of €0 — you never pay more than your flat price. To allow additional volume, raise the limit in your dashboard or remove it. Above it, the API blocks: you'll never be billed more than your limit.
Over your quota? No hard stop.
When your monthly quota is used up, your app just keeps running — every additional credit costs €0.001 billed transparently via Stripe. Requests only stop at the spending limit you set yourself.
Estimate your bill.
Move the sliders to your expected calls per month — we'll recommend the cheapest plan.
Overage requires a raised spending limit — by default you only pay the flat price. Currently available on monthly billing only.
This even fits the free Developer quota (non-commercial, for evaluation).
Compare all plans.
| Free | Pro | Scale | Enterprise | |
|---|---|---|---|---|
| Price/month | 0€ | 49€ | 199€ | individual |
| Modules | M1–M4 | M1–M4 | M1–M4 | M1–M4 |
| Included credits/month | 1,000 | 25,000 | 250,000 | ∞ |
| Overage per credit | — | €0.001 | €0.001 | — |
| Spending limit | — | €0 (adjustable) | €0 (adjustable) | — |
| Rate limit | 10 req/min | 300 req/min | 1200 req/min | individual |
| Commercial use | — | ✓ | ✓ | ✓ |
| Support | Community | Priority | Dedicated |