Install Jentic One Beta

Connect the MenuPlanner Web API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MenuPlanner Web API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmenuplanner.ru%2Fmenuplanner" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmenuplanner.ru%2Fmenuplanner" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MenuPlanner Web API.

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

GET STARTED

Start building with MenuPlanner Web API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MenuPlanner Web API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

31 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using MenuPlanner Web API through Jentic.

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.

Menuplanner Ru MenuPlanner Web API

AI ReadinessFoundational (D)46/100

See full scorecard

Community OpenAPI document · agent-readyProductivityCollaborationbearer, apiKey31 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: Generate a weekly menu plan, I want to generate a new recipe with AI, Parse a recipe from a web page, Invite someone to my household

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

64%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

51%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MenuPlanner Web API to your agent

Capabilities

Start building with MenuPlanner Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Menuplanner Ru MenuPlanner Web API

Jentic AI Readiness Score

MenuPlanner Web API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness