canonical: https://jentic.com/apis/thecocktaildb.com/thecocktaildb # TheCocktailDB API An open, crowd-sourced database of drinks and cocktails from around the world. The API exposes 5 endpoints. ## For AI agents Programmatically search cocktails, lookup cocktail or ingredient details. Covers 5 operations. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Search cocktails - Lookup cocktail or ingredient details - Get a random cocktail - Filter cocktails - List categories, glasses, ingredients, or alcoholic filters ## Use cases ### Developer Tools Operations Use the TheCocktailDB API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including search cocktails, lookup cocktail or ingredient details, get a random cocktail. Example prompt: Call GET /search.php to search cocktails ### Automated Filter.Php Management Automate filter.php operations by combining multiple TheCocktailDB API endpoints. Agents can lookup cocktail or ingredient details and then get a random cocktail in a single workflow. Example prompt: Call GET /lookup.php to lookup cocktail or ingredient details, then verify the result ### AI Agent Integration via Jentic AI agents discover and call TheCocktailDB 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 'search cocktails', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/search.php` | Search cocktails | | GET | `/lookup.php` | Lookup cocktail or ingredient details | | GET | `/random.php` | Get a random cocktail | | GET | `/filter.php` | Filter cocktails | | GET | `/list.php` | List categories, glasses, ingredients, or alcoholic filters | ## Key resources - **Filter.Php** — Operations for filter.php - **List.Php** — Operations for list.php - **Lookup.Php** — Operations for lookup.php - **Random.Php** — Operations for random.php - **Search.Php** — Operations for search.php ## 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:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/thecocktaildb.com/thecocktaildb/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 ``` ## Why Jentic - **Setup:** Wiring TheCocktailDB by hand means placing your API key in the path against www.thecocktaildb.com and handling each search and lookup endpoint yourself. Through Jentic you install once, import TheCocktailDB from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** TheCocktailDB is read-only, passing search and filter terms as query parameters on endpoints like /search.php and /lookup.php, so limit the agent to the operations it needs, such as searching cocktails or fetching a random drink. You choose that set, so an endpoint is only reachable if you include it. - **Credential handling:** Your TheCocktailDB 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 'search for a cocktail' or 'get a random drink recipe', and Jentic returns the matching TheCocktailDB 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 TheCocktailDB API use? The TheCocktailDB 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 cocktails with the TheCocktailDB 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 TheCocktailDB 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 cocktails through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search cocktails'. Jentic returns the matching TheCocktailDB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the TheCocktailDB API have? The TheCocktailDB API exposes 5 endpoints covering filter.php, list.php, lookup.php operations. ### Can I limit what my agent is allowed to do with the TheCocktailDB API? Yes. Because you run Jentic One yourself, you decide which of the five read-only TheCocktailDB operations your agent can reach, and any endpoint you leave out stays unreachable. If your agent only needs to look up drinks, you can allow just GET /search.php and GET /lookup.php while withholding GET /random.php, GET /filter.php, and GET /list.php. Since the API is read-only and takes search and filter terms as query parameters, scoping the operation set is what controls what the agent can do.