Food Info

Food Info serves harmonised nutrient data for reference foods over a versioned REST API. It merges six food-composition datasets — USDA FoodData Central, McCance & Widdowson's CoFID, ANSES Ciqual, DTU Frida, AUSNUT and Open Food Facts — into a single schema, so a caller can query nutrients across sources without reconciling each publisher's format. Endpoints cover food search, a full nutrient panel per food, a nutrient catalogue, reverse nutrient search for the richest and poorest reference foods, and recipe parsing and analysis that resolves raw ingredient lines into per-line nutrition. Authentication is an X-Api-Key header, with a free tier of 10 requests a minute and 100 a day. HTTPS only and CORS disabled, so it is built for server-to-server use. The underlying dataset carries a citable Zenodo DOI, which is unusual provenance for a commercial data API.

Food Info publishes 2 API contracts indexed on the APIs.io network: Recipes API and api v1 API. Tagged areas include Nutrition, Food, food-composition, Nutrients, and Data.

The Food Info catalog on APIs.io includes 1 Spectral governance ruleset.

Food Info’s developer surface includes documentation, authentication, support, code examples, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.7/100 thin ▬ flat Agent 30/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 published contract 1 MCP Servers 3 Agent Skills

Nutrition Food food-composition Nutrients Data Open DataDieteticsRecipes Health Research

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.7/100 · thin

Contract Quality 10.7 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 3.2 / 15

Operational Transparency 1.5 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/food-info/"><img src="https://apis.io/badge/food-info/card.svg" alt="Food Info on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 37.5 — up to +12.5 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/food-info/apis.yml: open an issue on github.com/api-evangelist/food-info to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

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

Food Info Recipes API

The RecipesApi API from Food Info — 2 operation(s) for recipesapi.

Food Info api v1 API

The api v1 API from Food Info — 6 operation(s) for api v1.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Food Info API V1 API

OPEN COLLECTION

Food Info Recipes API API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Food Info MCP Server

CANDIDATE MCP tool surface derived from the eight operations in the published OpenAPI. Food Info does NOT operate an MCP server — this is an API Evangelist proposal showing what...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Look up the nutrient panel for a food

AGENT SKILL

Analyse the nutrition of a recipe

AGENT SKILL

Find the foods highest or lowest in a nutrient

AGENT SKILL

Food Info API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Food Info Plans

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Food Info Rate Limits

2 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Food Info API Rules

54 rules · 51 errors 1 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Food Info Overlay

11 actions · documentation · food-info-openapi.json

DERIVED

Security Posture 3

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

Food Info Authentication

1 scheme

SECURITY

Food Info Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Food Info Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Food Info Agentic Access

8 operations · 2 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

LlmsText

WellKnown

MCPServer

AgentSkill

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

ErrorCatalog

Conventions

Lifecycle

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Examples

Examples

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: food-info
url: https://raw.githubusercontent.com/api-evangelist/food-info/refs/heads/main/apis.yml
name: Food Info
description: Food Info serves harmonised nutrient data for reference foods over a versioned REST API. It merges six food-composition
  datasets — USDA FoodData Central, McCance & Widdowson's CoFID, ANSES Ciqual, DTU Frida, AUSNUT and Open Food Facts — into
  a single schema, so a caller can query nutrients across sources without reconciling each publisher's format. Endpoints cover
  food search, a full nutrient panel per food, a nutrient catalogue, reverse nutrient search for the richest and poorest reference
  foods, and recipe parsing and analysis that resolves raw ingredient lines into per-line nutrition. Authentication is an
  X-Api-Key header, with a free tier of 10 requests a minute and 100 a day. HTTPS only and CORS disabled, so it is built for
  server-to-server use. The underlying dataset carries a citable Zenodo DOI, which is unusual provenance for a commercial
  data API.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/food-info.png
created: '2026-08-04'
modified: '2026-09-16'
specificationVersion: '0.23'
type: Index
position: Producing
access: 3rd-Party
kind: contract
tags:
- Nutrition
- Food
- food-composition
- Nutrients
- Data
- Open Data
- Dietetics
- Recipes
- Health
- Research
tags_raw:
- Nutrition
- Food
- Food Composition
- Nutrients
- Data
- Open Data
- Dietetics
- Recipes
- Health
- Research
apis:
- aid: food-info:food-info-recipesapi-api
  name: Food Info Recipes API
  description: The RecipesApi API from Food Info — 2 operation(s) for recipesapi.
  humanURL: https://food-info.org/developer
  baseURL: https://api.food-info.org
  tags:
  - RecipesApi
  properties:
  - type: OpenAPI
    url: openapi/food-info-recipesapi-api-openapi.yml
  - type: X-OpenAPI-Source
    url: https://api.food-info.org/api/v1/openapi.json
  - type: Documentation
    url: https://food-info.org/developer
  - type: Authentication
    url: authentication/food-info-authentication.yml
  - type: Plans
    url: plans/food-info-plans.yml
  - type: Conformance
    url: conformance/food-info-data-provenance.yml
  - type: X-DataSources
    url: https://food-info.org/data-sources
  - type: X-DatasetDOI
    url: https://doi.org/10.5281/zenodo.21527348
  - type: TermsOfService
    url: https://food-info.org/terms-conditions
  - type: PrivacyPolicy
    url: https://food-info.org/privacy-policy
  - type: LlmsText
    url: https://food-info.org/llms.txt
  - type: Examples
    url: examples/food-info-examples.yml
  - type: RateLimits
    url: rate-limits/food-info-rate-limits.yml
  - type: ErrorCatalog
    url: errors/food-info-problem-types.yml
  - type: Conventions
    url: conventions/food-info-conventions.yml
  - type: DataModel
    url: data-model/food-info-data-model.yml
  - type: ToolCrosswalk
    url: mcp/food-info-tool-crosswalk.yml
- aid: food-info:food-info-api-v1-api
  name: Food Info api v1 API
  description: The api v1 API from Food Info — 6 operation(s) for api v1.
  humanURL: https://food-info.org/developer
  baseURL: https://api.food-info.org
  tags:
  - ApiV1
  tags_raw:
  - api v1
  properties:
  - type: OpenAPI
    url: openapi/food-info-api-v1-api-openapi.yml
  - type: X-OpenAPI-Source
    url: https://api.food-info.org/api/v1/openapi.json
  - type: Documentation
    url: https://food-info.org/developer
  - type: Authentication
    url: authentication/food-info-authentication.yml
  - type: Plans
    url: plans/food-info-plans.yml
  - type: Conformance
    url: conformance/food-info-data-provenance.yml
  - type: X-DataSources
    url: https://food-info.org/data-sources
  - type: X-DatasetDOI
    url: https://doi.org/10.5281/zenodo.21527348
  - type: TermsOfService
    url: https://food-info.org/terms-conditions
  - type: PrivacyPolicy
    url: https://food-info.org/privacy-policy
  - type: LlmsText
    url: https://food-info.org/llms.txt
  - type: Examples
    url: examples/food-info-examples.yml
  - type: RateLimits
    url: rate-limits/food-info-rate-limits.yml
  - type: ErrorCatalog
    url: errors/food-info-problem-types.yml
  - type: Conventions
    url: conventions/food-info-conventions.yml
  - type: DataModel
    url: data-model/food-info-data-model.yml
  - type: ToolCrosswalk
    url: mcp/food-info-tool-crosswalk.yml
common:
- type: AgenticAccess
  url: agentic-access/food-info-agentic-access.yml
- type: DomainSecurity
  url: security/food-info-domain-security.yml
- url: https://food-info.org
  type: Website
- url: https://food-info.org/developer
  type: Documentation
- url: https://food-info.org/terms-conditions
  type: TermsOfService
- url: https://food-info.org/privacy-policy
  type: PrivacyPolicy
- url: https://food-info.org/llms.txt
  type: LlmsText
- url: authentication/food-info-authentication.yml
  type: Authentication
- url: plans/food-info-plans.yml
  type: Plans
- url: conformance/food-info-data-provenance.yml
  type: Conformance
- url: conformance/food-info-conformance.yml
  type: Conformance
- url: https://food-info.org/developer
  type: DeveloperPortal
- url: https://food-info.org/contact
  type: Support
- url: well-known/food-info-well-known.yml
  type: WellKnown
- url: well-known/food-info-security.txt
  type: SecurityTxt
- url: security/food-info-vulnerability-disclosure.yml
  type: VulnerabilityDisclosure
- url: https://food-info.org/.well-known/security.txt
  type: Security
- url: rate-limits/food-info-rate-limits.yml
  type: RateLimits
- url: errors/food-info-problem-types.yml
  type: ErrorCatalog
- url: conventions/food-info-conventions.yml
  type: Conventions
- url: lifecycle/food-info-lifecycle.yml
  type: Lifecycle
- url: data-model/food-info-data-model.yml
  type: DataModel
- url: mcp/food-info-mcp.yml
  type: MCPServer
- url: mcp/food-info-tool-crosswalk.yml
  type: ToolCrosswalk
- url: skills/_index.yml
  type: AgentSkill
- url: overlays/food-info-overlay.yaml
  type: Overlay
- url: examples/food-info-examples.yml
  type: Examples
- url: llms/food-info-llms.txt
  type: LLMsTxt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
X-Discovery:
  date: '2026-08-04'
  method: probed
  note: Requested in api-search/inbox#2. Every claim checked before profiling.
  findings:
  - surface: OpenAPI
    url: https://api.food-info.org/api/v1/openapi.json
    http_status: 200
    real: true
    note: OpenAPI 3.0.4, 8 operations, 24 schemas, X-Api-Key, real server. All 8 operations carry an operationId as of the
      2026-08-04 re-harvest — added by the provider the same day the gap was raised in api-search/inbox#2.
  - surface: LlmsTxt
    url: https://food-info.org/llms.txt
    http_status: 200
    real: true
    note: 8,462 bytes — LIVE. The submission said none was published; the provider confirmed it is server-generated rather
      than static, which is why it was overlooked. Re-fetched 2026-08-04 and byte-identical to the copy held.
  - surface: DatasetDOI
    url: https://doi.org/10.5281/zenodo.21527348
    http_status: 200
    real: true
    note: Resolves to Zenodo; a citable dataset record.
  - surface: DataSources
    url: https://food-info.org/data-sources
    http_status: 200
    real: true
  - surface: WellKnown
    url: https://food-info.org/.well-known/api-catalog
    http_status: 404
    real: false
    note: No RFC 9727 api-catalog on either host. A re-probe on 2026-08-04 did find an RFC 9116 security.txt at https://food-info.org/.well-known/security.txt
      (200) and a Content-Signal declaration in robots.txt; both are captured in well-known/.
  - surface: Control
    url: https://food-info.org/zzz-control-nonsense
    http_status: 404
    real: false
    note: Both hosts 404 correctly on a control path — no SPA catch-all, so the probes above are trustworthy.
  reharvests:
  - date: '2026-08-04'
    trigger: Provider reply on api-search/inbox#2
    note: Provider added operationIds to all 8 operations and confirmed the llms.txt. Spec re-fetched from the first-party
      source and archived verbatim to openapi/_original/.
    source: https://api.food-info.org/api/v1/openapi.json
    http_status: 200
    md5: 21560d8ec8635faec94658467f56d6c4
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Food Info API — frequently asked questions

Does Food Info have an API?

Yes. APIs.io lists 2 APIs from Food Info, including Food Info Recipes API and Food Info api v1 API.

Is there an OpenAPI specification for the Food Info API?

Yes. APIs.io indexes 2 OpenAPI specifications for Food Info, each linked for download from this page.

How do I authenticate with the Food Info API?

Food Info uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Food Info Authentication.

Does Food Info have an MCP server?

Yes. APIs.io lists 1 MCP server for Food Info: CANDIDATE MCP tool surface derived from the eight operations in the published OpenAPI. Food Info does NOT operate an MCP server — this is an API Evangelist proposal showing what one would look like, n

Is the Food Info API ready for AI agents?

Food Info has a Kin Score of 38.7 out of 100 (thin) and an Agent Readiness score of 29.8 (agent-ready), scored by API Evangelist on 2026-11-06.

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/food-info"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/food-info/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.