# Foodbe

> Foodbe is a food knowledge base for people and agents. It covers food science, food culture and history, cooking tips and tricks, substitutions and ingredients. Every answer is human-approved.

## Key facts

- Content model: three experts cover each topic from a different angle. Neuro covers science and nutrition, Oracle covers history and culture, Chefy covers cooking technique.
- If no approved answer exists, Foodbe says so and logs the question for review. It never guesses. Corrections can be reported to admin@foodbe.ai.
- GLP-1 coverage: Foodbe publishes non-promotional, sourced guidance on GLP-1 medication side effects: hydration, nausea, constipation, muscle loss, and appetite loss. It is grounded in real clinical and nutritional research, not medical advice.
- Ingredient pages: each ingredient has its own page with nutrition data, gut-health tags, flavor profile, allergen information, storage guidance, and linked recipes.
- Recipe pages: each recipe includes prep and cook time, nutrition breakdown, step-by-step instructions, and a related food-science fact.
- Structured data: recipe pages carry schema.org Recipe markup. Blog posts with FAQ-style accordion sections carry schema.org FAQPage markup.
- Shopping integration: recipe and blog pages with shoppable ingredients link to Instacart for one-click grocery ordering.
- Platform: Foodbe has an iOS app available on the App Store.
- Free resource: a GLP-1 hydration and side-effect cheat sheet is available by email signup.

## Pages

- [Homepage](https://www.foodbe.ai): Foodbe's entry point and product overview.
- [Blog index](https://www.foodbe.ai/blog): All published articles, ingredient pages, and GLP-1 guidance.
- [Recipes index](https://www.foodbe.ai/recipes): All published recipes with nutrition data.
- [GLP-1 Cheat Sheet](https://www.foodbe.ai/glp1-cheat-sheet): Free email-gated hydration and side-effect resource for GLP-1 medication users.

## URL patterns

- Ingredient and topic articles: `https://www.foodbe.ai/blog/{slug}`. One page per ingredient or food topic, each with its own nutrition data and facts.
- Recipes: `https://www.foodbe.ai/recipes/{slug}`. One page per recipe with full nutrition breakdown and instructions.

## Contact

- admin@foodbe.ai

## For agents

- No key needed for the first 5,000 free answers per IP address. Refusals are free.
- After that, get a free key with 5,000 tokens: POST to https://foodbe-v3-production.up.railway.app/v1/sandbox/register with email and appName. The reply includes an api_key.
- Send the key in the x-foodbe-key header.
- Each served answer uses one token. At zero balance the API returns 402.
- Paid bundles: Starter $99 for 10,000 tokens, Growth $299 for 50,000 tokens, Scale $999 for 150,000 tokens. Tokens never expire.
- Buy tokens: https://foodbe.ai/data#tokens
- If no approved answer exists, the reply has outcome "refused". Say so to your user instead of guessing.

## MCP and A2A

- MCP server (streamable HTTP): https://foodbe-v3-production.up.railway.app/v1/mcp
- MCP tools. The A2A skills have the same names. Every line comes from stored, human-approved data, never a model.
  - foodbe_cart_breakdown: call before you plan, comment on, improve or approve a grocery list or any set of foods. Send up to 50 ingredient names. Returns health labels, carbon and water totals, cart balance with the groups to add, the diets it suits, flavor and texture counts, the flavor gap, matching swaps and a cook's read for each food. The cook's read says how to cook the food, what to use if you run out and what it pairs with.
  - foodbe_query: call before you answer a question about food science, cooking technique, food culture, substitutions or ingredients. Returns one approved answer with sources.
  - foodbe_ingredient: call before you recommend or swap an ingredient. Returns allergens, swaps and storage for one ingredient.
  - foodbe_query_all: call when you need the next level of food data to better explain your food decisions. Returns the answers from Neuro, Oracle and Chefy.
  - foodbe_recipe_finder: call when a user asks for a recipe or for what to cook. Send a dish, with optional diet and allergies. Returns recipe cards with name, image, a short fact, servings, prep time, cook time and calories. If no recipe matches, it returns outcome "not_found" and costs nothing.
  - foodbe_meal_plan: call when a user asks for a meal plan or for what to eat over a number of days. All fields are optional: days from 1 to 7, a budget for the whole plan in US dollars, diet and allergies. Returns the plan and its insight. If no plan can be built, it returns outcome "not_found" and costs nothing.
  - foodbe_grocery_list: call when a user asks for a grocery or shopping list. Send a dish for one recipe, or days and a budget for a meal plan, with optional diet and allergies. Returns the list items with the cost of each and the total. If no list can be built, it returns outcome "not_found" and costs nothing.
  - foodbe_feedback: call when a Foodbe tool is missing, an answer was wrong or too thin, or a tool you need does not exist. Tell us what would help you. Send a message, with an optional kind (missing_tool, wrong_answer or other) and the tool name it concerns. Returns outcome "received". It is free and charges no tokens. The number of messages per day is limited.
- A2A endpoint (JSON-RPC, SendMessage): https://foodbe-v3-production.up.railway.app/v1/a2a
- A2A agent card: https://www.foodbe.ai/.well-known/agent-card.json
- MCP server card: https://www.foodbe.ai/.well-known/mcp/server-card.json
- AI catalog: https://www.foodbe.ai/.well-known/ai-catalog.json