Nutritionix
Nutritionix operates the world's largest verified nutrition database, exposing a Track API (v2) that converts natural-language food and exercise descriptions into full nutrient analysis, and powers food search, branded item lookup, and restaurant menu data for diet, fitness, and health applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Nutritionix the way a machine reads it — 70 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Nutritionix scores 56.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Nutritionix
Each block below is one kind of artifact we hold for Nutritionix. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Nutritionix Brands API
Search the database of food and restaurant brands.
Nutritionix Item API
Look up detailed nutrition for branded and restaurant menu items.
Nutritionix Natural Language API
Translate plain-text food and exercise phrases into structured nutrition data.
Nutritionix Search API
Search the nutrition database for common and branded foods.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Nutritionix Track API v2
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Nutritionix Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Nutritionix Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Natural Language Nutrition
Convert free-text meal descriptions into full nutrient breakdowns including calories, macros, and micronutrients.
Natural Language Exercise
Convert free-text activity descriptions into calorie-burn estimates personalized by gender, weight, height, and age.
Instant Food Search
Typeahead search returning matched common foods and branded foods for autocomplete experiences.
Branded & Restaurant Item Lookup
Retrieve detailed nutrition for branded grocery and restaurant menu items by nix_item_id or UPC.
Verified Nutrition Database
Access the world's largest verified nutrition database, including USDA NDB-linked common foods and over a million branded items.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Nutritionix Track Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Nutritionix API Rules
SPECTRALNutritionix API Rules
SPECTRALJSON Schema 15
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AltMeasure
JSON SCHEMABrand
JSON SCHEMABrandSearchResponse
JSON SCHEMABrandedFood
JSON SCHEMACommonFood
JSON SCHEMAExercise
JSON SCHEMAFood
JSON SCHEMAFoodsResponse
JSON SCHEMAFullNutrient
JSON SCHEMAInstantSearchResponse
JSON SCHEMANaturalExerciseRequest
JSON SCHEMANaturalExerciseResponse
JSON SCHEMANaturalNutrientsRequest
JSON SCHEMANaturalNutrientsResponse
JSON SCHEMAPhoto
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 15
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Track Alt Measure Structure
JSON STRUCTURETrack Brand Search Response Structure
JSON STRUCTURETrack Brand Structure
JSON STRUCTURETrack Branded Food Structure
JSON STRUCTURETrack Common Food Structure
JSON STRUCTURETrack Exercise Structure
JSON STRUCTURETrack Food Structure
JSON STRUCTURETrack Foods Response Structure
JSON STRUCTURETrack Full Nutrient Structure
JSON STRUCTURETrack Instant Search Response Structure
JSON STRUCTURETrack Natural Exercise Request Structure
JSON STRUCTURETrack Natural Exercise Response Structure
JSON STRUCTURETrack Natural Nutrients Request Structure
JSON STRUCTURETrack Natural Nutrients Response Structure
JSON STRUCTURETrack Photo Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 15
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Track Alt Measure Example
EXAMPLETrack Brand Example
EXAMPLETrack Branded Food Example
EXAMPLETrack Common Food Example
EXAMPLETrack Exercise Example
EXAMPLETrack Food Example
EXAMPLETrack Foods Response Example
EXAMPLETrack Full Nutrient Example
EXAMPLETrack Photo Example
EXAMPLEScroll within the panel for all 15 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Diet & Calorie Tracking
Power food logging and calorie-counting apps with natural-language meal entry.
Fitness & Activity Tracking
Estimate calories burned from logged workouts and activities.
Restaurant Menu Nutrition
Surface accurate nutrition facts for restaurant and chain menu items.
Nutrition Label Rendering
Generate FDA-style nutrition labels from API nutrient data.
Integrations 2
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
USDA NDB
Common-food results are linked to USDA National Nutrient Database (NDB) numbers and nutrient attribute IDs.
Syndigo / Riversand
Nutritionix is part of Syndigo; developer documentation is hosted on the Syndigo docs platform.
Resources
Every other property we hold for Nutritionix — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nutritionix · machine-readable index on apis.io