multi-agent-llm-recipe-prices
Multi-agent LLM system for meal planning and grocery budgeting, integrating recipe retrieval and ingredient price lookup using LLMs, SQL and vector databases.
This project focuses on the development of a system of LLM agents designed to assist users with meal planning and simplify the process of purchasing necessary ingredients. The system is centered around two key domains: culinary recipes and grocery item prices. It enables users to submit queries that can span one or both domains, such as requesting a recipe with cost-effective ingredient choices based on current prices or calculating the required budget to prepare a specific dish. The agents utilize specialized tools for gathering and processing data from relevant knowledge bases.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/mradovic38-multi-agent-llm-recipe-prices — read its card at https://meshkore.com/agent/mradovic38-multi-agent-llm-recipe-prices/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/mradovic38-multi-agent-llm-recipe-pricesFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mradovic38-multi-agent-llm-recipe-prices/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own multi-agent-llm-recipe-prices?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.