Install Jentic One Beta

Connect the TheMealDB API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TheMealDB 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthemealdb.com%2Fthemealdb" | sh

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%2Fthemealdb.com%2Fthemealdb" | 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 TheMealDB API.

Search meals

Lookup full meal details by ID

Get a random meal

List all meal categories

Monitor TheMealDB API operational status and events

Use Cases

GET STARTED

Start building with TheMealDB API

Explore with Jentic One

View OpenAPI Document

Automated Premium Management

Automate premium operations by combining multiple TheMealDB API endpoints. Agents can lookup full meal details by id and then get a random meal in a single workflow.

Call GET /lookup.php to lookup full meal details by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TheMealDB 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 'search meals', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — an open, crowd-sourced database of meals and recipes from around the world.

METHOD

PATH

DESCRIPTION

GET

/search.php

Search meals

GET

/lookup.php

Lookup full meal details by ID

GET

/random.php

Get a random meal

GET

/randomselection.php

Get 10 random meals (Premium only)

GET

/categories.php

List all meal categories

GET

/latest.php

Get latest meals (Premium only)

GET

/list.php

List categories, areas, or ingredients

GET

/filter.php

Filter meals

GET

/search.php

Search meals

GET

/lookup.php

Lookup full meal details by ID

GET

/random.php

Get a random meal

GET

/randomselection.php

Get 10 random meals (Premium only)

GET

/categories.php

List all meal categories

GET

/latest.php

Get latest meals (Premium only)

GET

/list.php

List categories, areas, or ingredients

GET

/filter.php

Filter meals

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring TheMealDB by hand means reading its key into the base path (the key sits in the URL as /api/json/v1/{apiKey}), splitting free from premium routes, and handling your own retries. Through Jentic you install once, import TheMealDB from the API Directory, store the key once, and your agent calls it.

Permission scoping

TheMealDB is read-only lookup and search, so scope it by operations: limit the agent to the calls it needs, such as searching meals or looking up a meal by id, and leave out routes you do not want it touching. Every operation you credit it with stays inside that allowed set.

Credential isolation

Your TheMealDB 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.

Intent-based discovery

Agents search Jentic by intent such as 'find a chicken recipe' or 'get a random meal', and Jentic returns the matching TheMealDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TheMealDB API through Jentic.

What authentication does the TheMealDB API use?

The TheMealDB 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 search meals with the TheMealDB API?

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

What are the rate limits for the TheMealDB 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 search meals through Jentic?

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

How many endpoints does the TheMealDB API have?

The TheMealDB API exposes 8 endpoints covering premium operations.

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

Yes. TheMealDB is read-only lookup and search, so with your self-hosted Jentic One instance you scope the agent by operation and grant only the calls it needs, such as searching meals with GET /search.php or looking up a meal by ID with GET /lookup.php. Your own rules decide which operations and credentials the agent may use, so you can leave out routes like the premium /randomselection.php or /latest.php endpoints that you do not want it touching. Every operation you credit the agent with stays inside that allowed set, and the stored API key is injected only for the calls you permit.

TheMealDB API

Name: TheMealDB API
Brand: TheMealDB API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlnone8 EndpointsREST

For Agents

Programmatically search meals, lookup full meal details by id. Covers 8 operations.

Use for: I need to meals, I want to lookup full meal details by id, Search for a random meal, Find all 10 random meals (premium only)

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

An open, crowd-sourced database of meals and recipes from around the world. The API exposes 8 endpoints.

Jentic One on Github View OpenAPI Document

Connect the TheMealDB API to your agent

Capabilities

Use Cases

Start building with TheMealDB API

Key Endpoints

Why Jentic?

Related APIs

FAQs

TheMealDB API