Track API
Community OpenAPI document · agent-readyDeveloper ToolsProject Managementnone4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically addpet, getfoods. Covers 4 operations.
Use for: I need to addpet, I want to getfoods, Search for findpetbyid, Find all deletepet
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API for Nutritionix Track application. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the Track API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Track 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.
1
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%2Ftrackapi%2Ftrackapi" | sh2
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%2Ftrackapi%2Ftrackapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Track API.
addPet
getFoods
findPetById
deletePet
Monitor Track API operational status and events
Use Cases
Patterns agents use Track API for, with concrete tasks.
★ Developer Tools Operations
Use the Track API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including addpet, getfoods, findpetbyid.
Call POST /foods to addpet
Automated foods Management
Automate foods operations by combining multiple Track API endpoints. Agents can getfoods and then findpetbyid in a single workflow.
Call GET /foods to getfoods, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Track API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'addpet', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — api for nutritionix track application.
METHOD
PATH
DESCRIPTION
POST
/foods
addPet
GET
/foods
getFoods
GET
/pets/{id}
findPetById
DELETE
/pets/{id}
deletePet
POST
/foods
addPet
GET
/foods
getFoods
GET
/pets/{id}
findPetById
DELETE
/pets/{id}
deletePet
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Track API by hand means pointing at the trackapi.nutritionix.com host, formatting its food and item requests, and coding your own response parsing. Through Jentic you install once, import the Track API from the API Directory, store any needed credential once, and your agent calls it.
Permission scoping
This Track API carries its target in the request body or a resource path, so scope the agent to the operations it needs, such as adding or listing foods. You choose which operations are allowed, so ones like deletion are left out unless you add them.
Credential isolation
Any Track API credential 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 'add a food' or 'list foods', and Jentic returns the matching Track API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Track API through Jentic.
What authentication does the Track API use?
The Track API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I addpet with the Track API?
Yes. Use the POST /foods endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Track API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I addpet through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'addpet'. Jentic returns the matching Track API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Track API have?
The Track API exposes 4 endpoints covering foods, pets operations.
Can I limit what my agent is allowed to do with the Track API?
Yes. Because you run Jentic One yourself, your own rules decide which Track API operations and credentials the agent may use. You can allow only the calls you want, such as adding a food with POST /foods and listing foods with GET /foods, while leaving out operations like DELETE /pets/{id} unless you explicitly permit them. The agent can then invoke only the endpoints you have scoped, so it cannot reach food or pet actions you have not approved.
GET STARTED