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

# Zestfuldata Zestful API

Recipe and Ingredient Analysis API that parses raw ingredient strings into structured JSON format with USDA database matching. The API exposes 1 endpoints.

## For AI agents

Programmatically parse ingredient strings. Covers 1 operations.

## Scope

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

## Capabilities

- Parse ingredient strings
- Manage developer tools data programmatically
- Integrate Zestful API into automated workflows
- Query and filter Zestful API records by parameters
- Monitor Zestful API operational status and events

## Use cases

### Developer Tools Operations

Use the Zestful API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including parse ingredient strings.

Example prompt: Call POST /parseIngredients to parse ingredient strings

### Data Retrieval and Monitoring

Query Zestful API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Zestful API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Zestful 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 'parse ingredient strings', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/parseIngredients` | Parse ingredient strings |

## Key resources

- **Parseingredients** — Operations for parseIngredients

## 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:** 75 / 100
- **Maturity:** AI-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 61 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/zestfuldata.com/zestfuldata/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 Zestful by hand means formatting each ingredient parse request against its single host and mapping the response fields yourself. Through Jentic you install once, import Zestful from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Zestful exposes a single ingredient-parsing operation, so scoping is operations-only: limit the agent to the parse operation it needs. You choose the operations it may call, so nothing beyond ingredient parsing runs unless you add it.
- **Credential handling:** Your Zestful 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 'parse ingredient strings', and Jentic returns the matching Zestful 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 Zestful API use?

The Zestful 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 parse ingredient strings with the Zestful API?

Yes. Use the POST /parseIngredients endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zestful 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 parse ingredient strings through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'parse ingredient strings'. Jentic returns the matching Zestful API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zestful API have?

The Zestful API exposes 1 endpoints covering parseingredients operations.

### Can I limit what my agent is allowed to do with the Zestful API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Zestful API exposes a single ingredient-parsing operation, POST /parseIngredients, so you scope the agent by granting only that operation. Nothing beyond ingredient parsing runs unless you add it.