Install Jentic One Beta

Connect the Open Brewery DB API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Brewery DB 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%2Fopenbrewerydb.org%2Fopenbrewerydb" | 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%2Fopenbrewerydb.org%2Fopenbrewerydb" | 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 Open Brewery DB API.

List breweries and filter by city, state, country, or postal code

Filter breweries by type or by distance from a point

Search breweries by free-text query

Look up a single brewery by its id

Read result metadata such as the total count for a filter

GET STARTED

Start building with Open Brewery DB API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Open Brewery DB API for, with concrete tasks.

★ City Brewery Discovery

A trip-planning agent lists breweries in a destination by calling GET /v1/breweries with the `by_city` filter. Each record includes an address and coordinates, so results drop straight onto a map or itinerary.

List the breweries in a given city and return their names and addresses for an itinerary

Proximity Search

To find breweries near a user, an agent calls GET /v1/breweries with the `by_dist` filter set to a latitude and longitude. This ranks results by distance so the closest options surface first.

Find the breweries closest to a coordinate and return the nearest few with their distance

Free-Text Brewery Search

When a user types a name or keyword, an agent calls GET /v1/breweries/search with a `query` to match across the directory. This handles fuzzy lookups where the exact city or id is not known.

Search the directory for a brewery by name and return the best matches

Single Brewery Lookup

Given a known id, an agent fetches the full record with GET /v1/breweries/{obdb_id} to get the address, phone, and website. This resolves a saved reference into current contact details.

Look up a brewery by its id and return its phone number and website

Key Endpoints

5 endpoints — the open brewery db api is a free directory of breweries, cideries, and brewpubs that an agent can search, filter, and look up by id.

METHOD

PATH

DESCRIPTION

GET

/v1/breweries

List and filter breweries

GET

/v1/breweries/{obdb_id}

Look up a brewery by id

GET

/v1/breweries/search

Search breweries by free text

GET

/v1/breweries/random

Return random brewery records

GET

/v1/breweries/meta

Read metadata for a query

GET

/v1/breweries

List and filter breweries

GET

/v1/breweries/{obdb_id}

Look up a brewery by id

GET

/v1/breweries/search

Search breweries by free text

GET

/v1/breweries/random

Return random brewery records

GET

/v1/breweries/meta

Read metadata for a query

Why Jentic?

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

Setup

Calling the Open Brewery DB API by hand means composing its filter and search parameters and paging through results yourself. Through Jentic you install once, import the API from the API Directory, and your agent lists, searches, and looks up breweries. No key is required.

Permission scoping

The API exposes read operations for listing, search, lookup, metadata, and random records, so scope by operation: allow an agent to list and search while leaving the random and metadata endpoints out of the allowed set until you add them.

Credential isolation

Open Brewery DB needs no API key, so there is no secret for Jentic to hold. Your own Jentic One instance still runs the calls, keeping execution on infrastructure you control.

Intent-based discovery

Agents search Jentic by intent such as 'find breweries in a city' or 'look up a brewery by id', and Jentic returns the matching Open Brewery DB operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Open Brewery DB API through Jentic.

What does the Open Brewery DB API do?

It is a free directory of breweries, cideries, and brewpubs. You can list and filter by city, state, country, postal code, type, or distance, search by free text, look up a brewery by id, and read metadata such as the total for a filter.

What authentication does the Open Brewery DB API use?

The specification declares no authentication, and the endpoints are public reads. An agent can call the directory operations without a key or token.

How do I find breweries in a city?

Call GET /v1/breweries with the `by_city` filter, and combine it with `by_type` or `by_dist` to narrow further. Each record includes an address and coordinates ready to map.

How do I look up a specific brewery?

Call GET /v1/breweries/{obdb_id} with the brewery's id to get its full record, including phone and website. Use GET /v1/breweries/search with a `query` when you only know the name.

What are the rate limits for the Open Brewery DB API?

The OpenAPI specification does not declare rate limits. Page through results with `per_page` and cache repeated lookups rather than polling tightly; confirm any limits in the Open Brewery DB documentation.

Do I need an MCP server to use the Open Brewery DB API with an agent?

You do not. Jentic connects the API to your agent directly from the API Directory: import it and the agent calls the search and lookup operations, with no key required.

Can I limit what my agent is allowed to do with the Open Brewery DB API?

Yes. Because you run Jentic One yourself, you choose the allowed operations: an agent can be permitted to list and search breweries while the random and metadata endpoints stay excluded, and every call still runs from your own instance.

Open Brewery DB API

Name: Open Brewery DB API
Brand: Open Brewery DB API
Availability: InStock

Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchnone5 EndpointsREST

For Agents

Search and filter breweries in Open Brewery DB by city, state, type, and distance, look up a brewery by id, and read result metadata.

Use for: I need a list of breweries in a given city, Find breweries near a set of coordinates, Search breweries by name, Look up a specific brewery by its id

Not supported: Does not handle reservations, reviews, or ordering. Use it to search, filter, and look up brewery listings and read result metadata only.

The Open Brewery DB API is a free directory of breweries, cideries, and brewpubs that an agent can search, filter, and look up by id. Listings can be filtered by city, state, country, postal code, type, and distance from a point, and a search endpoint matches free text against the directory. Each record carries the name, address, coordinates, phone, and website, so a result can be mapped or contacted directly. A meta endpoint reports totals for a query and a random endpoint returns sample records, which makes it handy for discovery apps, trip planning, and seeding demos with real place data.

Jentic One on Github View OpenAPI Document