Licensed bar data API: premises from public alcohol-licensing registers
Rows of licensed premises (bars, restaurants, taprooms and drink retail) derived from public
alcohol-licensing registers. Each row names its licence number and the register that issued it.
DrinkedIn also sells a cocktail recipe feed. Buy a monthly licence by card, or let an agent pay per
page over x402 with no account.
Counts are computed from the live queries that serve the public pages and the paid data feeds. Unvalidated venues are not counted.
Each number is a count of officially validated premises the paid bars feed can serve in that place, from the live sellable query. Unvalidated venues are not counted. A sample file has at most 50 premises for one place, and a phone or website only where that field's recorded provenance allows resale.
The buy button opens the card form on this page. That form posts to the existing Stripe checkout and does not charge until Stripe confirms payment. Per-record access is a request to the bars feed, which answers HTTP 402. Steps: x402 quickstart.
Download the city index (counts only). The example further down uses invented values. A city sample is rows from the sellable query.
A bars row from https://ai.drinkedin.net/api/data/v1/bars carries, among other fields:
license_id
The licence number, as the register publishes it. For a census row (madrid_censo) it is the census premises id, not a licence.
license_source
The register the row comes from, for example ny_sla or zurich_gastro. Its terms travel in source_notices on every response.
legal_name
The licensed legal entity, where the register publishes it.
license_term_start
When the current licence term started, where the register publishes it.
license_expires
When the licence expires, where the register publishes it.
name
The premises name as the register records it.
street_address
Street address, with postal_code, address_locality, address_region and address_country.
latitude
Coordinates (with longitude).
venue_category
What kind of premises it is (for example bar, restaurant, brewpub), with premise_type (on_premise, off_premise or producer).
phone
Phone and website, only where we can show they are redistributable; they carry the attribution notice served with the response.
DrinkedIn also records when a register last listed each premises. That date is not
part of the feed yet; the licence term dates above are, where the register publishes them.
A sample row
Illustrative: the field names are the feed's, the values are invented. This is not a
real premises.
Your licence key is emailed to you right after payment.
Card payment is handled by Stripe, and the licence renews monthly.
Bars
Licensed premises from public alcohol-licensing registers: bars, restaurants, taprooms and drink retail. One row per register entry, with its register id (a licence number, or a census premises id), street address and the register that listed it.
Source: government alcohol-licensing registers; phone and website, where present, from Overture Maps. Reuse terms differ by register: see the licence terms on this page.
$49 a month
or $0.005 per record over x402
Full data notes for developers
Alcohol premises from public registers — bars, restaurants, taprooms and drink retail. Each row names its source in `license_source`; most sources are alcohol-licensing registers, and those rows carry the licensed legal entity. Rows from a municipal premises census (`madrid_censo`) are premises listed in that census, not licences: their `license_id` is the census premises id and they have no licence status. Reproduce the `source_notices` served with each response (the Colorado disclaimer, attributions, scope notes). Every row has a venue_category/premise_type you can filter on. Distribution-only permits (wholesale, import, shipping) are excluded. Filter on `term_started_after` for recent licence activity -- new licences, renewals and operator changes, undifferentiated; NOT a newly-opened-premises signal. Includes street address and postal code on every row, licence number, the register legal name where held, and phone/website where we can show they are redistributable. Public-record provenance, and the licence rows carry no share-alike obligation -- but phone/website values are Overture-derived and DO require attribution. We do not record which upstream supplied a given value, so treat each as carrying CDLA-Permissive-2.0, Apache-2.0 and CC0-1.0 together, and reproduce the `contact_attribution` notice served with the response (DRI-423).
Cocktails
A cocktail recipe collection: name, ingredients and glass type for each recipe, with our own AI-generated description where we wrote one, and an image only where our own AI image generator made it (most recipes have none). No preparation steps. English only.
Source: the recipe text is a legacy import whose origin we have not established, and we do not claim it as ours; descriptions are AI-generated from each recipe's own facts; image rights are unconfirmed.
$29 a month
or $0.005 per record over x402
Full data notes for developers
~9.4k cocktail recipes: name, ingredients, glass type and the other recipe facts per row. WHAT SHIPS AS OURS: the `description` field, composed from that row's own recipe facts by our `cocktail_text_service.py`, AI-generated, labeled `first_party_generated_2026-09` in `description_provenance` and `true` in `description_ai_generated`; on any other row `description` is null. Images: `image_url` is served only for an image our own AI image generator (`cocktail_image_service.py`) made and recorded, with `image_provenance` `first_party_ai_generated` and `image_ai_generated` true; otherwise it is null. PROVENANCE of the existing imagery is not established (nothing stored tells a generated image from the legacy media library, whose per-image rights are unconfirmed), so today most or all rows carry no image. WHAT DOES NOT SHIP (since 2026-11-03): `recipe_instructions`, a legacy import whose origin is not established, and `video_url`; both keys are gone from every row. Also: `alcohol_content` is the constant 15.0 on every row -- a placeholder, not a measured ABV -- and `recipe_cuisine`, `recipe_category`, `recipe_yield`, `ice_type` and `equipment` each hold a single value corpus-wide. `garnish`, `calories` and `keywords` are empty. `difficulty_level` is "medium", `prep_time` 5, `average_rating` 0.0 and `total_ratings` 0 on every row, `total_time` is 10 and `is_classic` is false on every row -- the feed cannot identify a classic -- `created_by` is NULL throughout, and `is_alcoholic` is true on every row -- the feed cannot identify a mocktail. `glass_type` is null on about 4%. This feed ships NO translations. Ingredient splitting is unreliable: some rows are one un-split string, and others are an array broken at commas INSIDE product names ("6 oz sake rice wine5", "6 oz Mountain Dew(R) lime soda"), so a naive parser corrupts them either way. A page that returns rows requires payment or a licence. An empty page (zero matches, or an offset past the end) is not charged.
Per page, over x402 (no account)
A request that would return rows answers HTTP 402 with a quote
(bars $0.005 per record, cocktails $0.005 per record).
Pay that amount in USDC on Base, then retry the same request with the payment_id and
tx_hash. An empty page is not charged. Steps: x402 quickstart.
Each city page lists validated venues in that place and states its own count. Unvalidated venues are not counted.
Published venue pages
140486
https://drinkedin.net/bars/<slug>
One page per publishable validated venue. Unvalidated venues are not counted.
Published cocktail pages
9442
https://drinkedin.net/cocktails/<slug>
One page per published cocktail recipe that has a slug.
Licensable premises
4246
https://ai.drinkedin.net/api/data/v1/bars
Premises the paid bars feed can serve right now. Unvalidated venues are not counted.
Licensable cocktail recipes
9442
https://ai.drinkedin.net/api/data/v1/cocktails
Active cocktail recipes the paid cocktails feed can serve right now.
Licence
Bars data is derived from public registers. Each row carries its `license_source`; comply with that source's terms, which vary, and reproduce the `source_notices` served with each response. Zurich is CC0 and needs no attribution. Birmingham is OGL v3.0: credit it as "Contains public sector information licensed under the Open Government Licence v3.0." Colorado rows (co_lqr) come from the Colorado Information Marketplace, whose terms require the State of Colorado disclaimer (served in `source_notices`) wherever the data is shown. Texas rows (tx_tabc_mb) are the Texas Comptroller of Public Accounts, Mixed Beverage Tax Permits: mixed-beverage permits only. Maine BABLO rows must be credited as "Source: Maine Bureau of Alcoholic Beverages and Lottery Operations (BABLO) license data". Madrid rows (madrid_censo) are premises listed in Madrid's municipal premises census, not licences, and have no licence status: Ayuntamiento de Madrid — Censo de locales y sus actividades (dataset 200085-0-censo-locales, https://datos.madrid.es/dataset/200085-0-censo-locales), licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Cite the source and the update date, and do not suggest that the Ayuntamiento de Madrid takes part in, sponsors or endorses your use. Coordinates were converted from UTM ETRS89 zone 30N to WGS84, and rows are limited to open bar, cafeteria, copas and off-premise alcohol-retail activities. Rhode Island rows are not sold: that register publishes no reuse licence. No share-alike obligation applies to any of them. Where `contact_source` is an Overture token and the row carries `phone` or `website`, those served fields are Overture Maps **Places** data. Overture aggregates several upstreams under THREE licences -- CDLA-Permissive-2.0 (Meta, Microsoft, BrightQuery, DAC), Apache-2.0 (Foursquare) and CC0-1.0 (AllThePlaces). We hold a FEATURE-level source token, not a per-value one -- 2,467 of 3,971 rows carry both a phone and a website under a single token -- so we cannot say which licence covers a particular Overture value: treat every such value as carrying all three (DRI-423). None is share-alike, but two carry attribution duties; the notice to reproduce for those fields is `contact_attribution` on /bars, and it is present only when an Overture-sourced contact is in the payload. A row whose `contact_source` is `own_site` or `own_social` serves the phone and website the venue published on its own website or social page. Those fields are not Overture data. Each one carries `contact_field_attribution` with that source note and, when we stored it, the page URL. The CDLA notice does not cover them. Contacts we hold under a share-alike licence are withheld rather than served, so nothing in this feed obliges you to share alike.
Yes. GET https://ai.drinkedin.net/api/data/v1/bars returns licensed premises derived from public alcohol-licensing registers. Each row carries its register id (license_id: the licence number, or the premises id for a municipal census) and the register that listed it (license_source). A page that returns rows needs a licence key or an x402 payment; an empty page is not charged.
How do I buy a licence?
With a card: enter your email under Buy below or at https://drinkedin.net/pricing#data-licences and pay on Stripe ($49 a month for bars). Your licence key is emailed to you right after payment. Send it as the X-API-Key header.
Can an agent pay per page with x402, without an account?
Yes. A request that would return rows answers HTTP 402 with a quote ($0.005 per record). Pay that amount in USDC on Base, then retry the same request with the payment_id and tx_hash. The steps are in https://drinkedin.net/quickstart.md.
Can I use the data commercially?
The rows are sold for use under each register's terms, which travel with every row: license_source names the register, and the terms differ (some need attribution, some do not). Every response carries source_notices with the text each register requires you to reproduce, such as the State of Colorado disclaimer and the Open Government Licence credit. Phone and website values carry the attribution notice served with the response. The licence text on this page has the details; for anything it does not cover, write to [email protected].
Where do the cocktail recipes come from?
Each cocktail row's description_provenance field says whether its description was generated by DrinkedIn from that recipe's own facts. The recipe instructions are a legacy import of unestablished origin, and DrinkedIn does not represent them as its own to sublicense.