Mealie

Mealie is an open-source (AGPL-3.0), self-hosted recipe manager, meal planner and shopping-list application built on a FastAPI REST backend and a Vue frontend. Every feature in the UI is driven by the same public REST API: recipe CRUD and import-by-URL scraping, AI-assisted recipe creation, cookbooks, meal plans and mealplan rules, shopping lists and list items with cross-application "extras" key/value pairs, households and groups with multi-purpose labels, food/unit/tool organizers, a public "Explore" surface for unauthenticated browsing of shared content, scheduled webhooks, Apprise-backed event notifications, and admin backup/maintenance operations. The instance publishes its own OpenAPI 3.1 document and interactive Swagger UI at /openapi.json and /docs, authenticates with long-lived bearer API tokens (plus OIDC and LDAP for user login), and shares a uniform pagination, filtering and ordering grammar across nearly every collection endpoint.

Mealie publishes 1 API on the APIs.io network. Tagged areas include Company, Recipes, Food, Meal Planning, and Shopping Lists.

The Mealie catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Mealie’s developer surface includes documentation, API reference, getting-started guide, support, sandbox, changelog, and 14 more developer resources.

42.5/100 developing Agent 35/100 agent ready Full breakdown ↓
scored 2026-08-27 · rubric v0.15.1
1 APIs
CompanyRecipesFoodMeal PlanningShopping ListsSelf-HostedOpen SourceHouseholdNutritionHome Automation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-27 · rubric v0.15.1
Composite quality — 42.5/100 · developing
Contract Quality 12.4 / 25
Developer Ergonomics 13.8 / 20
Access Clarity 0.0 / 20
Operational Transparency 5.8 / 13
Contract Governance 3.6 / 12
Discoverability 6.9 / 10
Agent readiness — 35/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/mealie: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Mealie API

The Mealie REST API — 264 operations across 180 paths covering recipes, cookbooks, meal plans, shopping lists, households, groups, organizers, users, webhooks, event notificatio...

Pricing Plans 1

Published pricing tiers and plan structures.

Mealie Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Mealie Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Mealie Events

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Mealie Authentication

oauth2/http-bearer · 2 schemes

SECURITY

Mealie Domain Security

TLSv1.3 · HSTS

SECURITY

Mealie Vulnerability Disclosure

disclosure policy published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Mealie Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: mealie
name: Mealie
description: 'Mealie is an open-source (AGPL-3.0), self-hosted recipe manager, meal planner and shopping-list application
  built on a FastAPI REST backend and a Vue frontend. Every feature in the UI is driven by the same public REST API: recipe
  CRUD and import-by-URL scraping, AI-assisted recipe creation, cookbooks, meal plans and mealplan rules, shopping lists and
  list items with cross-application "extras" key/value pairs, households and groups with multi-purpose labels, food/unit/tool
  organizers, a public "Explore" surface for unauthenticated browsing of shared content, scheduled webhooks, Apprise-backed
  event notifications, and admin backup/maintenance operations. The instance publishes its own OpenAPI 3.1 document and interactive
  Swagger UI at /openapi.json and /docs, authenticates with long-lived bearer API tokens (plus OIDC and LDAP for user login),
  and shares a uniform pagination, filtering and ordering grammar across nearly every collection endpoint.'
image: https://avatars.githubusercontent.com/u/92342333?v=4
url: https://raw.githubusercontent.com/api-evangelist/mealie/refs/heads/main/apis.yml
x-type: company
x-source: harvest:health-device-stack
specificationVersion: '0.20'
created: '2026-08-27'
modified: '2026-08-27'
tags:
- Company
- Recipes
- Food
- Meal Planning
- Shopping Lists
- Self-Hosted
- Open Source
- Household
- Nutrition
- Home Automation
apis:
- name: Mealie API
  description: The Mealie REST API — 264 operations across 180 paths covering recipes, cookbooks, meal plans, shopping lists,
    households, groups, organizers, users, webhooks, event notifications and admin maintenance. Served by every Mealie instance
    from its own host; the project operates a public demo instance whose OpenAPI document is the harvested contract here.
  humanURL: https://docs.mealie.io/documentation/getting-started/api-usage/
  baseURL: https://demo.mealie.io/api
  tags:
  - Recipes
  - Meal Planning
  - Shopping Lists
  - Households
  properties:
  - type: OpenAPI
    url: openapi/mealie-openapi.json
  - type: Documentation
    url: https://docs.mealie.io/documentation/getting-started/api-usage/
  - type: APIReference
    url: https://demo.mealie.io/docs
  - type: Overlay
    url: overlays/mealie-openapi-overlay.yaml
  - type: Authentication
    url: authentication/mealie-authentication.yml
  - type: OAuthScopes
    url: scopes/mealie-scopes.yml
  - type: ErrorCatalog
    url: errors/mealie-problem-types.yml
  - type: DataModel
    url: data-model/mealie-data-model.yml
  - type: Conventions
    url: conventions/mealie-conventions.yml
  - type: RateLimits
    url: rate-limits/mealie-rate-limits.yml
  - type: Webhooks
    url: asyncapi/mealie-events.yml
  - type: Conformance
    url: conformance/mealie-conformance.yml
  - type: Lifecycle
    url: lifecycle/mealie-lifecycle.yml
  - type: Sandbox
    url: sandbox/mealie-sandbox.yml
  x-base-url-note: 'repair-api-bases.py returns `no-usable-base` for Mealie and it is right to flag it: demo.mealie.io is
    a demonstration host, not production. There IS no production host. Mealie is AGPL-3.0 self-hosted software, so the real
    base is templated — the docs say http(s)://<your-mealie-site>/api — and the only host the project itself operates and
    points integrators at is the public demo ("see the example at the Demo Site", https://docs.mealie.io/documentation/getting-started/api-usage/).
    baseURL is therefore recorded as https://demo.mealie.io/api: a real, reachable, provider-operated host that serves the
    harvested contract. The templated form https://{host}/api is carried in overlays/mealie-openapi-overlay.yaml, because
    the harvested spec declares no servers[] at all.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://mealie.io
- type: DeveloperPortal
  url: https://docs.mealie.io
- type: Documentation
  url: https://docs.mealie.io
- type: APIReference
  url: https://demo.mealie.io/docs
- type: GettingStarted
  url: https://docs.mealie.io/documentation/getting-started/introduction/
- type: Support
  url: https://github.com/mealie-recipes/mealie/discussions
- type: GitHubOrganization
  url: https://github.com/mealie-recipes
- type: SourceCode
  url: https://github.com/mealie-recipes/mealie
- type: Roadmap
  url: https://docs.mealie.io/documentation/getting-started/roadmap/
- type: Sandbox
  url: https://demo.mealie.io
- type: ChangeLog
  url: changelog/mealie-changelog.yml
- type: Releases
  url: https://github.com/mealie-recipes/mealie/releases
- type: Security
  url: security/mealie-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/mealie-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/mealie-domain-security.yml
- type: Packages
  url: packages/mealie-packages.yml
- type: Plans
  url: plans/mealie-plans-pricing.yml
- type: LLMsTxt
  url: llms/mealie-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: License
  url: https://github.com/mealie-recipes/mealie/blob/mealie-next/LICENSE
x-enrichment:
  date: '2026-08-27'
  status: enriched
  artifacts_added: 24
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/mealie"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/mealie/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/mealie/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.