LCBO API

Name: LCBO API
Brand: LCBO API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey12 EndpointsREST

For Agents

Search the LCBO product catalogue, locate Ontario LCBO stores, check live inventory levels, and pull producer and category metadata for retail and beverage applications.

Install Jentic One Beta

Connect the LCBO API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LCBO 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 LCBO API.

Search the LCBO product catalogue by name, category, or producer to power discovery features

Look up a specific product's full details including price, ABV, origin, and tasting notes

Find nearby LCBO stores by geolocation or postal code with hours and address data

GET STARTED

Start building with LCBO API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use LCBO API for, with concrete tasks.

★ Local Inventory Check for a Wine App

Build a consumer wine-discovery app that tells the user which nearby LCBO stores have a chosen bottle in stock. The agent geocodes the user's address, calls /stores to find the closest locations, then queries /inventories filtered by product and store to return live stock levels with the store distance and hours.

Given a productId and postal code, call /stores with a geo filter, then call /inventories filtered by productId and the top 5 storeIds and return the stores with quantity > 0.

Sommelier Recommendation Bot

Power a conversational sommelier that suggests LCBO products by varietal, region, or price band. The agent searches /products with category and price filters, retrieves tasting notes from /products/{id}, and presents three options ranked by price and rating. Useful for restaurants and consumer apps building over the LCBO catalogue.

Search /products with q='Pinot Noir' and price range $20-$40, then fetch /products/{id} for the top 3 results and return their tasting notes.

Bulk Catalogue Sync via Datasets

Cache the LCBO catalogue locally for analytics or e-commerce comparison. Agents pull the latest dataset snapshot via /datasets, ingest it into a warehouse, and then use the live product and inventory endpoints only for delta lookups. Reduces request volume against the live API while keeping local data fresh.

Call /datasets to find the most recent snapshot, fetch /datasets/{id}, download the referenced file, and load it into the local products table.

AI Agent Drinks Concierge via Jentic

An AI agent built on Jentic answers natural-language drinks questions: 'is the Penfolds Bin 389 in stock near downtown Toronto for under $90?' The agent uses Jentic to discover the matching LCBO operations, searches the product, finds the nearest stores, and checks inventory in one flow without hard-coded URLs.

Through Jentic, search 'find lcbo product in stock', execute /products with the product name, then chain to /stores and /inventories filtered by the resolved IDs.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for lcbo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

Search or list products in the catalogue

GET

/products/{id}

Get full details for a specific product

GET

/stores

Search or list Ontario LCBO stores

GET

/stores/{id}

Get details for a specific store

GET

/inventories

List inventory entries by product and store

GET

/categories

Browse the category tree

GET

/datasets

List dataset snapshots for bulk download

GET

/products

Search or list products in the catalogue

GET

/products/{id}

Get full details for a specific product

GET

/stores

Search or list Ontario LCBO stores

GET

/stores/{id}

Get details for a specific store

GET

/inventories

List inventory entries by product and store

Why Jentic?

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

Credential isolation

The LCBO API key is stored encrypted in the Jentic vault and applied as the `Authorization: Token <key>` header at execution time. The agent never sees the raw key.

Intent-based discovery

Agents search Jentic with intents like 'find lcbo product in stock' or 'list ontario liquor stores' and Jentic returns the matching LCBO operation with its input schema, so the right endpoint is selected without browsing docs.

Time to first call

Direct LCBO integration: half a day to wire auth, model the compound inventory ID, and chain product → store → inventory calls. Through Jentic: minutes — search, load schema, execute.

FAQs

Specific to using LCBO API through Jentic.

Why is there no official OpenAPI spec for LCBO API?

LCBO API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LCBO API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LCBO API use?

The LCBO API uses an API key passed in the `Authorization` header in the form `Token <your_key>`. Through Jentic, the key sits in the credential vault and is added to the header at execution time, so it never enters the agent context.

Can I check whether a product is in stock at a specific store?

Yes. Call GET /inventories with `product_id` and `store_id` filters, or use GET /inventories/{id} where the compound id encodes both. The response includes the current quantity, last reported time, and price at that store.

What are the rate limits for the LCBO API?

The LCBO API does not declare rate limits in its OpenAPI spec. The service is intended for non-commercial and developer use, so cache catalogue data locally with /datasets snapshots and reserve live calls for inventory and store lookups.

How do I find the nearest LCBO store to a postal code through Jentic?

Run `pip install jentic`, search 'find nearby lcbo stores', and execute GET /stores with the geo or postal code parameters. Jentic returns the matched stores ordered by distance with full address and hours.

Is the LCBO API free?

The LCBO API is free for non-commercial use with an API key. Commercial use cases should review the LCBO terms at lcboapi.com — Jentic does not change those terms.