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 APIs on the APIs.io network: API V1 API and Recipes API API. Tagged areas include Nutrition, Food, Food Composition, Nutrients, and Data.

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

🌐 Visit website 📡 Source on GitHub
38.0/100 thin ▬ flat Agent 46/100 agent ready Full breakdown ↓
scored 2026-08-12 · rubric v0.11.0
2 APIs 1 MCP Servers
NutritionFoodFood CompositionNutrientsDataOpen DataDieteticsRecipesHealthResearch

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-12 · rubric v0.11.0
Composite quality — 38.0/100 · thin
Contract Quality 12.0 / 21
Developer Ergonomics 6.2 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 1.7 / 11
Governance 1.2 / 10
Discoverability 7.4 / 9
Regulatory Posture 5.8 / 15
Agent readiness — 46/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 12 / 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 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.
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/. This rating is computed from github.com/api-evangelist/food-info: 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 2

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

Food Info API V1 API

The ApiV1 API from Food Info — 6 operation(s) for apiv1.

Food Info Recipes API API

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

MCP Servers 1

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

food-info-mcp.yml

MCP SERVER

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

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

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
AgenticAccess
 LlmsText
LlmsText
 WellKnown
WellKnown
 MCPServer
MCPServer
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Conventions
Conventions
 Lifecycle
Lifecycle
 DataModel
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)

apis.yml Raw ↑ 
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.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/food-info.png
created: '2026-08-04'
modified: '2026-08-04'
specificationVersion: '0.21'
type: Index
position: Producing
access: 3rd-Party
kind: contract
tags:
- Nutrition
- Food
- Food Composition
- Nutrients
- Data
- Open Data
- Dietetics
- Recipes
- Health
- Research
apis:
- aid: food-info:food-info-apiv1-api
  name: Food Info API V1 API
  description: The ApiV1 API from Food Info — 6 operation(s) for apiv1.
  humanURL: https://food-info.org/developer
  baseURL: https://api.food-info.org
  tags:
  - ApiV1
  properties:
  - type: OpenAPI
    url: openapi/food-info-apiv1-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-recipesapi-api
  name: Food Info Recipes API 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
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