CalorieKing Food API

Name: CalorieKing Food API
Brand: CalorieKing Food API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbasic8 EndpointsREST

For Agents

Search a curated nutrition database for foods, brands, categories, and tags, and retrieve detailed nutrient records by ID.

Install Jentic One Beta

Connect the CalorieKing Food API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CalorieKing Food 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 CalorieKing Food API.

Search the food catalog by keyword and filter results by brand, category, or tag

Retrieve a single food record with serving sizes and nutrient values via /foods/{foodId}

List and look up branded foods to attach packaged-product context to a meal log

GET STARTED

Start building with CalorieKing Food API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for CalorieKing Food API, keeping it validated and agent-ready. The CalorieKing Food API exposes a curated database of foods, brands, food categories, and dietary tags drawn from the long-running CalorieKing nutrition catalog. Agents can search foods by name, narrow results by brand or category, and retrieve a single food record with macronutrient and serving-size details. Filtering, paging, and partial-response query parameters keep payloads small for nutrition-tracking, meal-planning, and recipe-analysis workloads.

Use Cases

Patterns agents use CalorieKing Food API for, with concrete tasks.

★ Meal Logging and Calorie Tracking

Power a calorie-tracking app or agent that lets users log meals by searching the CalorieKing catalog. The /foods endpoint returns matching items with calorie and macronutrient data, and /foods/{foodId} retrieves a full nutrition record once the user picks an entry. Partial-response parameters keep mobile payloads small.

Search /foods for 'grilled chicken breast', present the top three matches to the user, then call /foods/{foodId} for the chosen item and return calories, protein, and fat per serving.

Branded Product Lookup for Recipe Apps

Recipe and pantry apps often need to attach branded product data to ingredient entries. The /brands and /brands/{brandId} endpoints let an agent confirm a brand exists in the catalog, then narrow a /foods search by brand to retrieve matching SKUs with packaged nutrition information.

Look up the brand 'Kelloggs' via /brands, then call /foods filtered by that brand to list cereal products with calories per serving.

Dietary Filtering for Meal Planners

Meal-planning agents need to surface foods that match dietary constraints. The /tags endpoint returns the catalog's dietary tags such as vegetarian or gluten-free, which can then be passed as a filter on /foods to retrieve only compliant items.

Fetch the tag list via /tags, find the 'gluten-free' tag ID, and call /foods filtered by that tag to return 20 gluten-free options with calorie counts.

AI Agent Nutrition Workflows via Jentic

Through Jentic, an AI agent discovers CalorieKing operations by intent, loads the input schema for /foods, and executes a search without browsing docs or handling Basic Auth tokens directly. Jentic's vault holds the access token used as the Basic Auth username, so the agent only sees scoped tool results.

Use the Jentic SDK to search for 'find food nutrition', load the /foods operation schema, and execute it with a query for 'oatmeal' to return the top result's calorie value.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for calorieking food api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/foods

Search and list foods with filters

GET

/foods/{foodId}

Retrieve a specific food's nutrition record

GET

/brands

List food brands

GET

/categories

List food categories

GET

/tags

List dietary tags

GET

/foods

Search and list foods with filters

GET

/foods/{foodId}

Retrieve a specific food's nutrition record

GET

/brands

List food brands

GET

/categories

List food categories

GET

/tags

List dietary tags

Why Jentic?

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

Credential isolation

The CalorieKing access token is stored encrypted in the Jentic vault. Agents receive scoped execution rights and Jentic injects the token into the HTTP Basic Auth username at call time, so the raw secret never enters the agent's context.

Intent-based discovery

Agents search by intent (for example, 'find food nutrition') and Jentic returns the matching CalorieKing operation along with its input schema, so the agent can call /foods or /foods/{foodId} without browsing the developer portal.

Time to first call

Direct CalorieKing integration: half a day to a day for token handling, base64 Basic Auth wiring, and pagination handling. Through Jentic: under one hour to search, load, and execute.

FAQs

Specific to using CalorieKing Food API through Jentic.

Why is there no official OpenAPI spec for CalorieKing Food API?

CalorieKing does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CalorieKing Food API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the CalorieKing Food API use?

The API uses HTTP Basic authentication. The access token issued by CalorieKing is used as the username and the password is left blank. When called through Jentic, the access token is stored in the Jentic vault and injected into the Basic Auth header at execution time, so it never enters the agent's prompt context.

Can I retrieve the full nutrition profile for a specific food?

Yes. Call GET /foods/{foodId} with the ID returned from a /foods search to retrieve the full record, which includes serving sizes and nutrient values. Use partial-response query parameters if you only need a subset of fields.

How do I filter foods by dietary tag through Jentic?

First call GET /tags to retrieve the list of dietary tags and find the ID for the tag you need (for example, gluten-free). Then call GET /foods with the tag filter applied. Through Jentic, search 'find food by dietary tag', load the /foods schema, and execute with the tag ID parameter.

What are the rate limits for the CalorieKing Food API?

The OpenAPI specification does not document rate limits. CalorieKing applies limits at the access-token level based on your developer plan, so check the agreement attached to your token. Jentic surfaces 429 responses unchanged so your agent can back off and retry.

Does the API return branded product nutrition data?

Yes. Use GET /brands to discover available manufacturers, then filter GET /foods by brand to return that brand's products with calorie and macronutrient values per serving.