canonical: https://jentic.com/apis/trackapi/trackapi

# Track API

API for Nutritionix Track application. The API exposes 4 endpoints.

## For AI agents

Programmatically addpet, getfoods. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- addPet
- getFoods
- findPetById
- deletePet
- Monitor Track API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'addpet', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/foods` | addPet |
| GET | `/foods` | getFoods |
| GET | `/pets/{id}` | findPetById |
| DELETE | `/pets/{id}` | deletePet |

## Key resources

- **foods** — Operations related to foods
- **pets** — Operations related to pets

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 35 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/trackapi/trackapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.