OpenMenu API

Name: OpenMenu API
Brand: OpenMenu API
Availability: InStock

✓ Official Vendor SpecData EnrichmentCompany DataapiKey11 EndpointsREST

For Agents

Search restaurants and menus, look up nutrition and ingredient data, and pull DishDNA ML-derived analytics on dishes and trends.

Install Jentic One Beta

Connect the OpenMenu API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenMenu 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 OpenMenu API.

Search restaurants, menus, and individual menu items by keyword or location

Retrieve restaurant details including menu structure and contact information

Look up ingredient and nutrient data for specific menu items

GET STARTED

Start building with OpenMenu API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use OpenMenu API for, with concrete tasks.

★ Restaurant Discovery by Location

Build a discovery surface that shows restaurants near a user's location with their current menus and active deals. The agent calls /location to find nearby restaurants, /restaurant for details, and /deals to surface active offers. Search results can be filtered by menu content using the /search endpoint.

Call GET /location with the user's coordinates, then for the top three restaurants call GET /deals and return the list of currently active deals.

Nutrition Lookup for a Dish

Surface calorie, ingredient, and nutrient data for a chosen menu item by calling /menu_items to find the item and /ingredients to retrieve its breakdown. This is useful for dietary apps, allergen filters, and calorie-conscious menu UIs.

Search /menu_items for 'caesar salad', take the top result's item ID, and call /ingredients to return its calorie and macronutrient values.

Trend Spotting with DishDNA Analytics

Identify which dishes are gaining traction in a region by combining the /trends endpoint with DishDNA-powered /analysis_search results. Outputs feed editorial roundups, retailer assortment decisions, and menu-engineering work.

Call GET /trends scoped to a chosen city, then return the top 10 trending menu items with their growth signal.

AI Agent Restaurant Assistant via Jentic

An assistant that helps users pick a restaurant or check what is on a menu can call OpenMenu through Jentic. The api_key is vaulted, calls are routed by intent, and the structured menu response keeps the LLM grounded in real menu items rather than hallucinated dishes.

Use Jentic to search for 'find restaurants near a location', execute GET /location with the coordinates, and return the names and addresses of the top five matches.

Key Endpoints

11 endpoints — openmenu provides a structured catalogue of restaurant menus, menu items, and nutritional and ingredient data, enriched with dishdna machine-learning analysis.

METHOD

PATH

DESCRIPTION

GET

/search

Search restaurants, menus, and menu items

GET

/restaurant

Get restaurant details

GET

/location

Find restaurants near a location

GET

/menu

Get menu items and taxonomies

GET

/menu_items

Search menu items

GET

/ingredients

Get ingredient and nutrient data

GET

/deals

Get deals and coupons

GET

/trends

Get trending menu items

GET

/search

Search restaurants, menus, and menu items

GET

/restaurant

Get restaurant details

GET

/location

Find restaurants near a location

GET

/menu

Get menu items and taxonomies

GET

/menu_items

Search menu items

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The api_key query parameter is stored in the MAXsystem vault and appended to each request automatically, so it never appears in agent prompts or logs.

Intent-based discovery

Agents search Jentic with intents like 'find restaurants near a location' or 'get nutrition for a dish' and receive the matching OpenMenu operation with its query parameters, ready to execute.

Time to first call

Direct integration: 1-2 days to handle auth, search shape, and DishDNA endpoint conventions. Through Jentic: under 1 hour.

FAQs

Specific to using OpenMenu API through Jentic.

What authentication does the OpenMenu API use?

API key authentication via the api_key query parameter. Through Jentic the key is stored in the MAXsystem vault and added to the request URL automatically, so it does not appear in agent logs.

Can I look up nutrition data for menu items with the OpenMenu API?

Yes. GET /ingredients returns ingredient and nutrient data for menu items, and /menu_items can be used to find the item ID first. This is the standard path for dietary or calorie-aware features.

What are the rate limits for the OpenMenu API?

OpenMenu does not publish a single global rate limit; it depends on the API plan. Cache restaurant and menu responses client-side and contact OpenMenu before high-volume bulk pulls.

How do I find restaurants near a location with the OpenMenu API through Jentic?

Search Jentic for 'find restaurants near a location', load GET /location, and execute it with latitude and longitude query parameters. Jentic appends the api_key from the vault.

What is DishDNA in the OpenMenu API?

DishDNA is OpenMenu's machine-learning layer that classifies and ranks menu items. The /analysis, /analysis_search, /trends, and /heatmap endpoints expose DishDNA-derived signals such as taxonomies and trend scores on top of the raw menu data.

Can I retrieve active restaurant deals with the OpenMenu API?

Yes. GET /deals returns deals and coupons currently published for restaurants in the catalogue, scoped by the supplied query parameters.