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

# ReciPal API

Nutrition label and recipe management API. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create recipe, list recipes. Covers 5 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create recipe
- List recipes
- Get recipe
- Generate nutrition label
- Access ReciPal API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the ReciPal API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including create recipe, list recipes, get recipe.

Example prompt: Call POST /recipes to create recipe

### Automated Ingredients Management

Automate ingredients operations by combining multiple ReciPal API endpoints. Agents can list recipes and then get recipe in a single workflow.

Example prompt: Call GET /recipes to list recipes, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ReciPal 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/recipes` | Create recipe |
| GET | `/recipes` | List recipes |
| GET | `/recipes/{id}` | Get recipe |
| GET | `/ingredients` | List ingredients |
| GET | `/labels` | Generate nutrition label |

## Key resources

- **Ingredients** — Ingredients operations
- **Recipes** — Recipes operations
- **Labels** — Labels operations

## Why Jentic

- **Setup:** Wiring the ReciPal API by hand means learning its apiKey auth, pointing at the recipal.com host, and handling requests yourself. Through Jentic you install once, import the ReciPal API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** ReciPal puts the recipe id in the URL path (`/recipes/{id}`), so a rule can pin your agent to specific recipes alongside its read-only ingredient and label lookups. You choose the operations it may call, so creating a recipe is only included if you add it.
- **Credential handling:** Your ReciPal 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a recipe' or 'look up an ingredient', and Jentic returns the matching ReciPal 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 ReciPal API use?

The ReciPal API uses an API key passed in the `X-API-Key` header. 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 create recipe with the ReciPal API?

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

### What are the rate limits for the ReciPal 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 create recipe through Jentic?

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

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

The ReciPal API exposes 5 endpoints covering ingredients, recipes, labels operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ReciPal operations and credentials the agent can use, so you can allow only read-only lookups like listing ingredients (GET /ingredients) and generating nutrition labels (GET /labels) while withholding recipe creation (POST /recipes). Since ReciPal puts the recipe id in the URL path (GET `/recipes/{id}`), a rule can pin the agent to specific recipes rather than all of them. Creating a recipe is included only if you explicitly add that operation.