Dining

Read Dining: one record by id, restaurants filtered by status, city, cuisine or text (with meal aggregates), or meals filtered by restaurant, dates or dish text. No filter gives headline counts, top restaurants and recent meals. Use for dining QUESTIONS; never to look up an ID before logging a meal, dining_add resolves a restaurant by name on its own.

Note: No filter returns headline counts, top restaurants and recent meals; type 'restaurant' with status 'want_to_try' and a city reads the want-to-try list.

{}

Add one record in a single call: a meal (pass the restaurant by NAME, restaurantName, as the user said it: it is matched case-insensitively or created, so never look up an ID first; date is the only other requirement; capture every dish named, ratings only when stated), or a restaurant for the list (type 'restaurant': name, city, recommendedBy). A real record.id updates that record instead.

Note: Pass a meal's restaurant by name as the user said it; Vritto finds or creates it.

{
  "record": {
    "restaurantName": "Kasama",
    "date": "2026-09-25",
    "mealType": "dinner",
    "rating": 4.5,
    "totalCostAmount": 96,
    "totalCostCurrency": "USD",
    "dishes": [
      {
        "name": "Pork adobo",
        "rating": 5,
        "wouldOrderAgain": true
      },
      {
        "name": "Ube basque cake",
        "rating": 4
      }
    ]
  }
}

Change one meal or restaurant by record.id (set type 'restaurant' for a restaurant); only sent fields change. A meal's dishes are written whole: echo each kept dish's id. Resolve the id with dining_find first, or reuse the id a dining_add just returned.

Note: A meal's dishes are written whole: echo each kept dish's id.

{
  "record": {
    "id": "meal_123",
    "rating": 5
  }
}

Remove (archive) one meal, or one restaurant from the list (its meals keep their history). Only for explicit removals; resolve the id first.

Note: Set type 'restaurant' to remove a restaurant; its meals keep their history.