The world's
dietary pulse
Anonymised, aggregated food intelligence derived from real dining behaviour. Allergen trends, intolerance prevalence, diet adoption, cuisine popularity — all via a single REST API.
curl https://api.chez-vous.co/v1/dietary/allergens \
-H "X-API-Key: cvk_your_key_here" \
-G -d "country_code=FR&limit=5"
{
"data": [
{ "allergen": "gluten", "prevalence": 0.124, "cohort": "100–499", "country": "FR" },
{ "allergen": "dairy", "prevalence": 0.098, "cohort": "100–499", "country": "FR" },
{ "allergen": "peanuts", "prevalence": 0.041, "cohort": "50–99", "country": "FR" },
{ "allergen": "tree_nuts", "prevalence": 0.038, "cohort": "50–99", "country": "FR" },
{ "allergen": "eggs", "prevalence": 0.029, "cohort": "10–49", "country": "FR" }
],
"updated_at": "2026-05-28T02:00:00Z"
}Free tier · 100 requests/day · No credit card
Privacy by design
k-Anonymity enforced in every row
No personal data ever enters the Chez Vous database. Every ETL job applies strict k-anonymity (k ≥ 10): cohorts below the threshold are silently dropped before writing. Cohort sizes are bucketed in API responses — you know the signal is real without knowing who generated it.
- ✓No PII — ever. Enforced at ETL, not just at query time.
- ✓Cohort sizes bucketed: 10–49, 50–99, 100–499, 500+
- ✓City-level data suppressed for small cohorts
- ✓Read-only connection to source data — no write-back possible
ETL pipeline — each nightly job
Aggregate Chez Moi data
Read-only query on source tables
Drop cohorts < 10
k-anonymity filter_rows(k_min=10)
Suppress small cities
suppress_city() applied on location field
Write to metrics DB
Only anonymised aggregate rows land here
API buckets cohort_size
"52" → "50–99" · no raw count exposed
API surface
Nine endpoints, nine data dimensions
Updated nightly from Chez Moi diner data. All responses are JSON, paginated, and filterable by country, city, and date range.
/v1/dietary/allergensfreeAllergen prevalence by country, city, and demographic cohort
/v1/dietary/intolerancesfreeIntolerance rates with severity breakdown
/v1/dietary/dietsfreeDiet adoption (vegan, keto, halal, kosher, …)
/v1/dietary/trendsstarterMonthly deltas — which diets are rising or falling
/v1/cuisine/popularitystarterCuisine preference by geography and occasion
/v1/ingredients/demandstarterIngredient demand index tied to seasonal and event patterns
/v1/events/occasionsproOccasion-to-cuisine mapping for event catering intelligence
/v1/restaurants/*enterpriseAnonymised restaurant-level benchmarks and feedback analytics
/v1/health/*enterpriseDietary risk aggregates cross-referenced with health outcomes
Pricing
Start free, scale as you grow
Explore the API and validate fit.
- ✓
/dietary/allergens - ✓
/dietary/intolerances - ✓
/dietary/diets
For teams building food-aware features.
- ✓
Everything in Free - ✓
/dietary/trends - ✓
/cuisine/popularity - ✓
/ingredients/demand
For production data pipelines.
- ✓
Everything in Starter - ✓
/events/occasions
Full access, SLA, and dedicated support.
- ✓
Everything in Pro - ✓
/restaurants/* - ✓
/health/*
Who uses Chez Vous
Eight industries, one data feed
Any team that makes decisions based on what people eat — or don't eat — benefits from Chez Vous.
Grocery retailers
Shelf placement driven by real dietary adoption curves
Food brands
R&D informed by allergen and intolerance trends
Health insurers
Population dietary risk stratification
Pharma & nutrition
Diet-condition correlation research
Food delivery
Menu curation and recommendation tuning
Meal kit companies
Box composition optimised to subscriber profiles
Public health agencies
Regional dietary surveillance without PII
PE funds & analysts
Dietary macro trends for food sector due diligence
Data quality
Fresh, consistent, reliable
Nightly ETL
Seven jobs run between 02:00 and 05:00 UTC each night. Data is always within 24 hours of source activity.
Geographic coverage
Filtered by country and city for markets where Chez Moi has sufficient diner density to meet k-anonymity thresholds.
Trend history
Monthly deltas going back to launch. Plot adoption curves, detect emerging dietary shifts, and track seasonal patterns.
Start with a
free API key
100 requests per day on the free tier — enough to prototype, validate your use case, and see real dietary data before committing to a plan.