RecipeBee for agents
RecipeBee developer resources
RecipeBee exposes a public REST API and a remote MCP server so 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.
- MCP server card
Discovery document for MCP clients.
- 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.
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.
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.