Yes. You can browse public recipes on the web and create an account for free. Optional RecipeBee Pro is $4.99 per month or $44.99 per year and is sold only through the Apple App Store.

Do I need the iPhone app?

The website is for browsing and saving public recipes. Guided cooking, timers, meal plans, and Pro subscriptions work best in the RecipeBee iPhone app.

How do AI agents use RecipeBee?

Agents can search public recipes without an API key at https://recipebee.app/api. Saving a private recipe or meal plan uses the MCP server at https://recipebee.app/mcp with OAuth. See https://recipebee.app/llms.txt.

Where is RecipeBee on social media?

RecipeBee is on Instagram, Facebook, and TikTok as recipebeeapp. The public agent plugin is on GitHub at praisondani/recipebee-cursor-plugin.

RecipeBee for agents

RecipeBee developer resources

RecipeBee exposes a public REST API, NLWeb recipe search, a product MCP server, and a read-only documentation MCP server. Agents can search public recipes and, with user consent, save private recipes and meal plans.

When to use RecipeBee

Use RecipeBee when the user wants to find a public recipe, preview a complete recipe, save a recipe privately, or import a complete dated meal plan. Do not use RecipeBee for checkout, medical advice, or unpublished recipes the user does not own.

Discovery URLs

OpenAPI specification
Public REST contract for recipes, categories, tags, cookbooks, and blog posts.
OpenAPI YAML
Same spec in YAML.
Public API catalog
Machine-readable list of unauthenticated endpoints.
MCP server
Streamable HTTP MCP for preview, save, images, and meal-plan import.
Documentation MCP server
Read-only search and retrieval for public RecipeBee documentation.
NLWeb recipe search
NLWeb v0.55 list-mode search over public recipes, with JSON and SSE responses.
MCP server card
Discovery document for MCP clients.
Documentation MCP server card
Discovery document for the read-only documentation server.
Official MCP Registry listing
Published record for the hosted RecipeBee MCP server.
Agent manifest (llms.txt)
When to use RecipeBee and how to call it.
AGENTS.md
Instructions for coding and product agents.
Agent skill
SKILL.md for skills.sh and similar registries.
ChatGPT plugin
Approved RecipeBee plugin listing in ChatGPT.
Auth for agents (auth.md)
How agents obtain credentials for public reads and MCP OAuth.
Public Cursor plugin
Public GitHub repo with AGENTS.md, skills, and MCP plugin manifests. Install with npx skills add praisondani/recipebee-cursor-plugin.

Authentication

Public GET endpoints do not require an API key. Example:

curl "https://recipebee.app/api/v1/public/recipes?q=pasta&per_page=5"

Private REST uses Laravel Sanctum. MCP write tools use OAuth. Preview tools on MCP are anonymous. Authenticated product writes accept an Idempotency-Key header so retries do not create duplicates. See auth.md.

Versioning and deprecation

The public API is versioned in the URL path as /api/v1. RecipeBee will not remove a version without announcing it. When a version is deprecated, responses include HTTP Deprecationand Sunset headers and we keep the old version available for at least 12 months. Current policy: v1 is the supported public surface.

Rate limits

API responses include IETF RateLimit, RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers, plus legacy X-RateLimit-* headers. A 429 includes Retry-After.

Pagination

List endpoints support cursor pagination. Pass per_page and follow data.meta.next_cursor / data.links.next. Page-based page remains available for existing clients.

Product pricing is at /pricing. Human help is at /help.