Norish

Norish is an open-source, self-hosted recipe and meal-planning application built for households — import a recipe from a URL, video or photo, plan the week on a shared calendar, and keep a grocery list that every member of the household sees update in real time. It is distributed as a Docker image (norishapp/norish) under AGPL-3.0 and runs entirely on the operator's own hardware, with PostgreSQL, Redis and a Python parser service behind it. Each instance exposes an HTTP API under /api/v1 — recipes, recipe imports, groceries, stores and planned recipes — secured with an instance-issued API key, plus a generated OpenAPI document and a Scalar API reference that are served from the running instance to signed-in users.

Norish publishes 1 API on the APIs.io network. Tagged areas include Company, Recipes, Meal Planning, Groceries, and Food.

Norish’s developer surface includes documentation, getting-started guide, support, changelog, API reference, authentication, and 17 more developer resources.

🌐 Visit website 📡 Source on GitHub

24.5/100 emerging ▬ flat Agent 9/100 agent aware Front door AI 3/6 light open core · AGPL-3.0 Full breakdown ↓
scored 2026-10-04 · rubric v0.23.0

AccessOpen

1 API

Company Recipes Meal Planning Groceries Food Self-Hosted Open Source Household CalendarCalDAV

Kin Score

Kin Score How this is scored →
scored 2026-10-04 · rubric v0.23.0

Composite quality — 24.5/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 9.6 / 17

Access Clarity 0.0 / 17

Operational Transparency 4.4 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 9/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 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 Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/norish: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Norish Recipe API

The HTTP API each Norish instance serves under /api/v1, covering a public health check plus authenticated recipe read/search/create/import, grocery list management, stores, and ...

Pricing Plans 1

Published pricing tiers and plan structures.

Norish Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Norish Rate Limits

1 limits

RATE LIMITS

Security Posture 2

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

Norish Authentication

0 schemes

SECURITY

Norish Domain Security

TLSv1.3

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conformance

Conventions

Idempotency

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

SourceCode

SourceCode

Packages

Packages

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

License

License

Plans

Plans

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: norish
name: Norish
description: Norish is an open-source, self-hosted recipe and meal-planning application built for households — import a recipe
  from a URL, video or photo, plan the week on a shared calendar, and keep a grocery list that every member of the household
  sees update in real time. It is distributed as a Docker image (norishapp/norish) under AGPL-3.0 and runs entirely on the
  operator's own hardware, with PostgreSQL, Redis and a Python parser service behind it. Each instance exposes an HTTP API
  under /api/v1 — recipes, recipe imports, groceries, stores and planned recipes — secured with an instance-issued API key,
  plus a generated OpenAPI document and a Scalar API reference that are served from the running instance to signed-in users.
deliveryModel:
  model: open-core
  license: AGPL-3.0
  license_evidence:
    repo: norish-recipes/norish
    spdx: AGPL-3.0
    stars: 1229
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: medium
  source:
  - pricing
  - repository-license
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://raw.githubusercontent.com/norish-recipes/norish/main/.github/assets/logo.svg
url: https://raw.githubusercontent.com/api-evangelist/norish/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'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Recipes
- Meal Planning
- Groceries
- Food
- Self-Hosted
- Open Source
- Household
- Calendar
- CalDAV
tags_raw:
- Company
- Recipes
- Meal Planning
- Groceries
- Food
- Self-Hosted
- Open Source
- Household
- Calendar
- CalDAV
- Open-Source
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: norish:norish-recipe-api
  name: Norish Recipe API
  description: The HTTP API each Norish instance serves under /api/v1, covering a public health check plus authenticated recipe
    read/search/create/import, grocery list management, stores, and planned recipes for today/week/month. Authenticated with
    an instance-issued API key passed as x-api-key or as an Authorization Bearer token. Because Norish is self-hosted there
    is no vendor base URL — the host is the operator's own instance, so the base is templated.
  humanURL: https://docs.norish.dev/reference/api
  baseURL: https://{norish-instance-host}/api/v1
  tags:
  - Recipes
  - Groceries
  - Meal Planning
  - Stores
  - Calendar
  properties:
  - type: APIReference
    url: https://docs.norish.dev/reference/api
  - type: Documentation
    url: https://docs.norish.dev/
  - type: Authentication
    url: authentication/norish-authentication.yml
  - type: Conventions
    url: conventions/norish-conventions.yml
  - type: Idempotency
    url: conventions/norish-conventions.yml
  - type: RateLimits
    url: rate-limits/norish-rate-limits.yml
  - type: DataModel
    url: data-model/norish-data-model.yml
common:
- type: DomainSecurity
  url: security/norish-domain-security.yml
- type: Website
  url: https://norish.dev
- type: Documentation
  url: https://docs.norish.dev/
- type: GettingStarted
  url: https://docs.norish.dev/quick-start
- type: GitHubOrganization
  url: https://github.com/norish-recipes
- type: SourceCode
  url: https://github.com/norish-recipes/norish
- type: Support
  url: https://github.com/norish-recipes/norish/issues
- type: License
  url: https://github.com/norish-recipes/norish/blob/main/LICENSE
- type: Packages
  url: packages/norish-packages.yml
- type: Lifecycle
  url: lifecycle/norish-lifecycle.yml
- type: ChangeLog
  url: changelog/norish-changelog.yml
- type: Conformance
  url: conformance/norish-conformance.yml
- type: Plans
  url: plans/norish-plans-pricing.yml
- type: LLMsTxt
  url: llms/norish-llms.txt
- type: X-MCPServerCandidate
  url: mcp/norish-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DeveloperPortal
  url: https://docs.norish.dev/
- type: APIReference
  url: https://docs.norish.dev/reference/api
- type: Authentication
  url: authentication/norish-authentication.yml
- type: Conventions
  url: conventions/norish-conventions.yml
- type: Idempotency
  url: conventions/norish-conventions.yml
- type: RateLimits
  url: rate-limits/norish-rate-limits.yml
- type: DataModel
  url: data-model/norish-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-27'
  status: enriched
  artifacts_added: 18
  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/norish"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/norish/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/norish/evidence"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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