Install Jentic One Beta

Connect the Chomp Food Database API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chomp Food Database API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchompthis.com%2Fchompthis" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchompthis.com%2Fchompthis" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Chomp Food Database 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

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Chomp Food Database 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Chomp Food Database by hand means passing its api_key as a query parameter and picking the right branded lookup among barcode, name, and search endpoints. Through Jentic you install once, import the Chomp Food Database API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Chomp takes its lookup terms as query parameters rather than resource ids in the URL path, so scope the agent to the operations it needs, such as barcode lookup and ingredient search. Every Chomp operation here reads data, so the agent only queries the food database.

Credential isolation

Your Chomp api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a food product by barcode' or 'search branded foods', and Jentic returns the matching Chomp operation with its query parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Chomp Food Database 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.

Can I limit what my agent is allowed to do with the Chomp Food Database API?

Yes. Because you run Jentic One yourself, your own rules decide which Chomp operations and credentials the agent may use, so you can grant only the endpoints it needs, such as barcode lookup at /food/branded/barcode.php and ingredient search at /food/ingredient/search.php, while withholding name lookup and branded search. Chomp takes its lookup terms as query parameters rather than resource ids in the path, so the scope you set governs which operations run rather than which records are touched. Every Chomp operation here is read-only, so a scoped agent only queries the food database and never writes to it.

Chompthis Chomp Food Database API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey4 EndpointsREST

For Agents

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

Use for: I need to look up a food item by its barcode, Get the nutrition facts for a branded grocery product, Search for all branded foods made by a given brand, Find the allergens listed on a packaged food

Not supported: Does not handle recipe parsing, meal planning, or restaurant menu data - use for branded food and ingredient lookups only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

81%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Chomp Food Database API to your agent

Capabilities

Start building with Chomp Food Database API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Chompthis Chomp Food Database API

Jentic AI Readiness Score

Chomp Food Database API Documentation

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness