
The AI Dietician
A cloud-native multi-agent meal planning platform for patients managing diet-responsive conditions and for athletes, built around South Asian food.
Problem
General nutrition tools assume Western food and ignore clinical constraints. A diabetic patient in Karachi eating roti, daal and rice gets nothing usable from them, and a wrong carbohydrate number is not a rounding error.
Approach
Four LangGraph agents — Intake, RAG Researcher, Diet Planner, Clinical Critic. The Critic is deliberately independent, because a check performed by the same context that produced the plan is worth far less.
Dual-store retrieval — Postgres for exact nutrition lookups, Pinecone for narrative clinical guidance. Vector similarity is the wrong tool for exact numeric facts.
Two-stage retrieval — a bi-encoder recall gate using bge-large-en-v1.5, then a cross-encoder reranker for precision on the shortlist.
The model never computes nutrition. It selects food IDs and gram amounts; a deterministic Python solver performs every arithmetic operation.
Hard safety refusals for pregnancy, type 1 diabetes, advanced CKD, users under 15, and underweight weight-loss requests, with handoff to a certified dietician. Under-15 users are excluded from expert contact at the API layer.














- Agents in pipeline
- 4
- Client surfaces
- 3
- Retrieval stages
- 2
- Backing data stores
- 2
- Safety refusal classes
- 5
- SQA test cases
- 30
- Defects catalogued
- 15