canonical: https://jentic.com/apis/menuplanner.ru/menuplanner

# Menuplanner Ru MenuPlanner Web API

The MenuPlanner Web API powers a household meal-planning app, generating weekly menu plans and new recipes with AI and extracting recipes from a URL. It manages a household's members and invitations, lets each user build a personal recipe collection and copy recipes shared by the household, and maintains the user profile and its linked Yandex account. A voice route handles Yandex Alice requests on top of the same recipe and menu data.

## For AI agents

Generate weekly menu plans and recipes with AI, parse recipes from a URL, manage household members and invitations, and build a personal recipe collection. Backs a shared household meal-planning app.

## Scope

Does not process payments, send marketing email, or manage inventory. Use for household meal planning, recipe collection, and AI menu generation only.

## Capabilities

- Generate a weekly menu plan from available recipes
- Generate a new recipe or a dish image with AI
- Parse a recipe from a URL using AI extraction
- Invite, list, resend, and remove household members
- Add recipes to a personal collection or copy them from the household
- Maintain the user profile and its linked Yandex account

## Use cases

### Agent-planned weekly menu

An AI assistant plans the week's meals for a household by generating a menu from the recipes available to it. The MenuPlanner Web API returns a weekly plan from a menu-generation operation and can create missing recipes or a dish image on demand. Through Jentic the agent discovers these operations by intent and the session credential is injected at call time.

Example prompt: Generate a weekly menu plan from the household's recipes and create a dish image for any recipe that lacks one

### Household recipe collaboration

Families share recipes across a household rather than keeping separate copies. The MenuPlanner Web API invites and lists household members, copies a recipe from the household into a personal collection, and adds or removes recipes from that collection, so an agent can keep each member's cookbook in sync with what the household shares.

Example prompt: Invite a new household member, list the current members, and copy a shared recipe into the new member's personal collection

### AI recipe import

Users often want a recipe they found on a web page added to their collection. The MenuPlanner Web API parses a recipe from a URL with AI extraction and can generate a new recipe from a prompt, so an agent can turn a link or an idea into a structured recipe the household can plan around.

Example prompt: Parse a recipe from a given URL and add the extracted recipe to the user's collection

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/generate-menu` | Generate a weekly menu plan from available recipes |
| POST | `/api/generate-recipe` | Generate a recipe with AI |
| POST | `/api/parse-recipe` | Parse a recipe from a URL using AI extraction |
| POST | `/api/invitations/create` | Create a household invitation |
| GET | `/api/household/members` | Get household members |
| POST | `/api/recipes/copy-from-household` | Copy a household recipe to a personal collection |

## Key resources

- **AI** — Generate menus, recipes, and dish images and parse recipes from a URL
- **Recipes** — Add recipes to a personal collection and copy recipes shared by the household
- **Household** — List and remove household members
- **Invitations** — Create, list, resend, accept, and delete household invitations
- **Profile and Yandex** — Update the profile, delete the account, and manage the linked Yandex account

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 46 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 21 / 100
  - Agent Usability: 94 / 100
  - Security: 63 / 100
  - AI Discoverability: 51 / 100
- **View full report:** https://jentic.com/apis/menuplanner.ru/menuplanner/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the MenuPlanner Web API by hand means handling the JWT bearer and session-cookie login, telling the public routes from the signed-in ones, and managing the OAuth flow yourself. Through Jentic you install once, import it from the API Directory, store the session credential once, and your agent calls it.
- **Permission scoping:** MenuPlanner carries recipe and household targets in the request body and session, so rules bound which operations your agent may call, such as generating menus and listing recipes. You choose the operation set, so the account-deletion and member-removal operations are not included unless you add them.
- **Credential handling:** Your MenuPlanner session credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate a weekly meal plan' or 'parse a recipe from a URL', and Jentic returns the matching MenuPlanner operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Spoonacular** — Spoonacular supplies recipe search, meal planning, and nutrition data from a large recipe database.
- **Edamam** — Edamam offers recipe search and nutrition analysis APIs.
- **Nutritionix** — Nutritionix returns nutrition facts for foods and dishes.

## FAQ

### What authentication does the MenuPlanner Web API use?

Most endpoints need a signed-in session, carried either as a JWT bearer token or as a session cookie, per its OpenAPI spec, while some public and OAuth routes do not. Through Jentic the session credential is stored once and injected at call time, so it never enters the agent's prompt, logs, or context.

### Can I generate a weekly menu with the MenuPlanner Web API?

Yes. A menu-generation operation builds a weekly plan from the recipes available to the household, and recipe-generation and dish-image operations can fill in anything missing. An agent can request a plan and then create any recipe or image the plan references.

### What are the rate limits for the MenuPlanner Web API?

The OpenAPI spec does not define numeric rate limits, and AI generation routes can be slower than the data routes. Have your agent back off when it receives an HTTP 429 response and space out the generation calls.

### Is there a MenuPlanner MCP server?

You don't need an MCP server to give your agent the MenuPlanner Web API. Jentic connects it directly from the API Directory: import it, store your session credential once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with the MenuPlanner Web API?

Yes. MenuPlanner carries recipe and household targets in the request body and session, so rules bound which operations your agent may call, such as generating menus and listing recipes, rather than which recipe. The account-deletion and member-removal operations are not included unless you add them, and every call it makes is logged.

### How do I generate a weekly menu through Jentic?

Search Jentic for an intent such as 'generate a weekly meal plan' and it returns the matching menu-generation operation with its input schema, so your agent requests the plan and reads it back. To run it on your own infrastructure, install Jentic One from its GitHub repo.