Chomp Food Database API

Name: Chomp Food Database API API
Brand: Chomp Food Database API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey4 EndpointsREST

For Agents

Look up branded food products by barcode, name, or search terms — returns nutrition facts, ingredients, allergens, and package data.

Quickstart

Get started with Chomp Food Database API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up a food product by barcode"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chomp Food Database API API.

Resolve a UPC or EAN barcode to a branded food item with full nutrition facts via /food/branded/barcode.php

Look up a branded grocery product by its name through /food/branded/name.php

Search the branded food catalogue with brand, category, and ingredient filters via /food/branded/search.php

Retrieve raw and generic ingredient data including macronutrient breakdowns from /food/ingredient/search.php

GET STARTED

Start building with Chomp Food Database API API

Explore with Jentic

View OpenAPI Document

Chomp is a food and nutrition database that exposes branded grocery products and generic ingredients through a barcode, name, and search-based API. The service returns nutritional facts, ingredient lists, allergens, package size data, and brand metadata for millions of consumer packaged goods. It is used by health and wellness apps, recipe builders, grocery apps, and dietary tracking tools that need structured food data without crawling supermarket sites. The API is read-only and queried with simple GET requests authenticated by an API key passed in the query string.

Use Cases

Patterns agents use Chomp Food Database API API for, with concrete tasks.

★ Barcode-Driven Grocery App

A grocery shopping or pantry-tracking app scans a UPC barcode and needs immediate nutrition and allergen information for the product. The /food/branded/barcode.php endpoint accepts the barcode digits and returns the matching product record with calories, macros, ingredient list, and brand metadata. This eliminates the need to maintain an in-house product database that quickly goes stale.

Look up the product with barcode 049000028911 via /food/branded/barcode.php and return calories, total fat, and allergen list

Recipe Nutrition Calculator

A recipe app needs to compute total nutrition for a dish from its ingredient list. The /food/ingredient/search.php endpoint returns per-100g macronutrient data for raw ingredients like chicken breast, olive oil, or onions, which the app multiplies by quantity to produce a recipe-level nutrition panel. This is more accurate than relying on user-entered values.

Search /food/ingredient/search.php for 'chicken breast' and return protein, fat, and carbohydrate values per 100g

Allergen and Diet Filtering

A diet-aware shopping assistant filters products to only those compatible with a user's restrictions — gluten-free, dairy-free, peanut-free. The /food/branded/search.php endpoint allows ingredient and category filtering, and the response payload includes allergen flags so the application can exclude unsafe products before showing them to the user.

Search /food/branded/search.php for cereals, exclude items containing gluten, and return the top 20 results

Agent-Driven Pantry Inventory

An AI agent helping a user log their pantry calls Chomp through Jentic to resolve scanned barcodes into structured product records. The agent searches Jentic for 'look up a food product by barcode', loads the operation, and executes against each scan. Jentic isolates the API key and returns scoped operations the agent can call without managing credentials directly.

Search Jentic for 'look up a food product by barcode', load the barcode operation, and resolve five scanned UPCs to product records

Key Endpoints

4 endpoints — chomp is a food and nutrition database that exposes branded grocery products and generic ingredients through a barcode, name, and search-based api.

METHOD

PATH

DESCRIPTION

GET

/food/branded/barcode.php

Get a branded food item by barcode

GET

/food/branded/name.php

Get a branded food item by name

GET

/food/branded/search.php

Search branded foods with filters

GET

/food/ingredient/search.php

Search generic ingredient nutrition data

GET

/food/branded/barcode.php

Get a branded food item by barcode

GET

/food/branded/name.php

Get a branded food item by name

GET

/food/branded/search.php

Search branded foods with filters

GET

/food/ingredient/search.php

Search generic ingredient nutrition data

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Chomp api_key is stored encrypted in the Jentic vault. Agents receive scoped access — the raw key is never injected into prompts or context windows.

Intent-based discovery

Agents search by intent (e.g., 'look up a food product by barcode') and Jentic returns the matching Chomp operation with its query parameter schema.

Time to first call

Direct integration: 1-2 hours for auth, request signing, and response parsing. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Edamam

Food and nutrition database covering recipes, ingredients, and branded products

Choose Edamam when you need recipe parsing or nutrition analysis on free-text ingredient lists rather than barcode lookup

Alternative

Spoonacular

Recipe and food product database with meal planning endpoints

Choose Spoonacular when the application needs recipe search and meal planning in addition to product lookups

Complementary

Nutritionix

Natural-language nutrition lookup for restaurant and common foods

Pair with Chomp when users enter free-text descriptions like '2 eggs and toast' rather than scanning barcodes

FAQs

Specific to using Chomp Food Database API API through Jentic.

What authentication does the Chomp Food Database API use?

Chomp uses an API key passed as the api_key query parameter on every request. Through Jentic, the key is stored encrypted in the vault and the agent receives a scoped reference rather than the raw key value.

Can I look up a product by UPC barcode with the Chomp Food Database API?

Yes. The /food/branded/barcode.php endpoint accepts a UPC or EAN barcode and returns the matching branded product with nutrition facts, ingredient list, allergen flags, and brand metadata in a single response.

Does Chomp return allergen information?

Yes. Branded food responses include allergen fields parsed from product packaging, covering common allergens such as milk, eggs, peanuts, tree nuts, soy, wheat, fish, and shellfish where the source data lists them.

What are the rate limits for the Chomp Food Database API?

Rate limits are tied to your subscription tier on chompthis.com/api rather than declared in the OpenAPI spec. Plan to throttle requests and back off on HTTP 429 responses; check your account dashboard for the current monthly quota.

How do I look up a food product by barcode through Jentic?

Run pip install jentic, search for 'look up a food product by barcode', load the /food/branded/barcode.php operation, and execute with the barcode value. Jentic appends the API key from the vault and returns the parsed product record.

Can I search for ingredients rather than branded products?

Yes. The /food/ingredient/search.php endpoint covers raw and generic ingredients such as chicken breast or olive oil and returns macronutrient data per 100g, which is what you need for recipe-level nutrition calculation.