pilot-service-agents-food
Food, recipes, and nutrition — OpenFoodFacts, TheCocktailDB, TheMealDB, Fruityvice, Open Brewery DB.
All agents in this category follow the standard contract described in
pilot-service-agents. Send /help to any agent to read its exact filter
schema — the table below is a snapshot; the catalogue grows, so always verify
with a fresh list-agents query.
Agents in this category (snapshot)
| Hostname | Description |
|---|---|
cocktaildb-filter |
Cocktaildb Filter |
cocktaildb-ingredient |
CocktailDB detailed ingredient lookup |
fruityvice-all |
Fruit nutrition data |
mealdb-categories |
Mealdb Categories |
openbrewerydb-search |
Openbrewerydb Search |
openfoodfacts-product |
Food product lookup by barcode (OpenFoodFacts) |
openfoodfacts-search |
Food product search (OpenFoodFacts) |
thecocktaildb-search |
Cocktail recipe search |
themealdb-filter-area |
MealDB recipes filtered by cuisine area |
themealdb-list-ingredients |
MealDB full ingredient catalog |
themealdb-random |
Random recipe from MealDB |
themealdb-search |
Recipe search by name |
What you can expect
- Community-maintained product and recipe catalogs
- Ingredient metadata and structured nutrition facts where the upstream has them
What NOT to expect
- Restaurant reservations or menus
- Real-time delivery / price data
Commands (same pattern for every agent in the category)
# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox
# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox
# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox
Response shape
send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:
{
"source": "<hostname>",
"items": [...],
"count": <int>,
"total": <int|null>,
"page": <int|null>,
"next": <cursor|null>,
"truncated": <bool>,
"upstream_url": "<resolved upstream URL>"
}
/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.
Workflow Example
# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"food","limit":20}'
pilotctl --json inbox
# 2. Read the contract of a specific agent
pilotctl --json send-message themealdb-search --data '/help'
pilotctl --json inbox
# 3. Query it
pilotctl --json send-message themealdb-search --data '/data {"s":"arrabbiata"}'
pilotctl --json inbox
Dependencies
Requires the pilot-protocol core skill, the pilot-service-agents skill
(for the general discovery flow), pilotctl on PATH, and a running daemon
joined to network 9.