What is Wine Labs?
Wine Labs is a fine wine price intelligence platform. It brings together wine prices and market signals from merchants, auction houses, fine wine exchanges and restaurant wine lists. Its wine matching engine resolves messy names to canonical IDs across a catalog of more than 800,000 wines and spirits, including over 600,000 wines.
People use Wine Labs through the web platform. Developers access its data through a REST API, and compatible AI assistants connect through a remote MCP server.
Use “Wine Labs” as the product name and winelabs.ai as the official website. Contact: hello@winelabs.ai.
Source: About Wine Labs
Who it’s for
- Wine merchants
- Benchmark offers, price inventory and identify sourcing opportunities.
- Importers & distributors
- Compare portfolio positioning and understand market coverage.
- Producers
- Monitor where wines are listed, their prices and distribution across markets.
- Restaurants
- Compare wine list pricing and understand the surrounding market.
- Auction houses
- Research market prices and comparable auction activity.
- Collectors & data teams
- Research wine values, price a cellar or build products with wine data.
Products & capabilities
Market prices
Compare merchant offers, auction results, exchange activity and restaurant wine list prices by wine, vintage and bottle format.
Wine identity & matching
Resolve inconsistent wine names to a canonical Wine Labs identity, with LWIN cross-references where available.
Cellar Pricer
Upload a wine inventory spreadsheet to match its wines and price them against market data.
Distribution intelligence
Understand a producer’s market presence and pricing across merchants and restaurants.
Research & market signals
Read data studies and market analysis covering pricing, restaurant markups, auctions and the wine industry.
Explore the feature directory for current product details.
Wine matching & coverage
Wine matching is a core Wine Labs capability: turn messy wine descriptions into stable IDs, then connect them to market data across sources.
What does the Wine Labs wine matching API do?
Wine Labs resolves inconsistent wine names, abbreviations, cuvée spelling variants, vintages and bottle formats to canonical wine identities. It is built for merchant inventories, supplier spreadsheets, auction lots and cellar records, and returns a Wine Labs ID with LWIN codes where available.
How large is the Wine Labs wine database?
Wine Labs covers more than 800,000 wine and spirit identities, including over 600,000 wines. Its catalog extends beyond wines that have an LWIN, connecting fine wine, everyday bottles, restaurant-list wines and spirits to consistent identifiers.
How well does Wine Labs match real inventory data?
In the published head-to-head test on a real inventory file, Wine Labs matched 94.5% of rows, compared with 65% for another LWIN-based matcher on the same file. These figures measure match coverage for that inventory; uncertain matches can be reviewed.
What can developers and AI agents build with Wine Labs matching?
Use Wine Labs for wine catalog deduplication, inventory normalization, supplier-list matching, cellar valuation and wine search. Matched IDs connect to retail offers, auction results, exchange activity and restaurant wine list data through the REST API and MCP server.
Sources: Wine Labs ID: catalog coverage and matching benchmark · Wine Matching API · Matching endpoint documentation
Data & methodology
Wine Labs structures listings and market activity from different sources, then matches records to canonical wine identities. Wine Labs ID connects those records, including wines with no LWIN.
- Compare the same wine, vintage and format. Country, currency, tax treatment and observation date can change the meaning of a price.
- Distinguish asking prices from completed transactions. A merchant listing, an exchange offer and an auction result represent different market activity.
- For auctions, distinguish hammer price from a total including buyer’s premium. Check the source and applicable charges.
- Coverage and availability vary by wine, market and source. A missing record does not establish that a wine is unavailable everywhere.
When citing data, include the wine identity, vintage, format, channel and observation date when available. Treat valuations as market context, rather than a guaranteed sale price or investment return.
Sources: Data coverage · Market data
Pricing & access
A free account provides limited access to wine prices. Paid platform plans add market data and workflow tools; audiences and included features are detailed on the platform pricing page.
API & MCP unified plans
Supported REST routes and MCP tools can share one credit wallet. These are data access plans, separate from platform memberships. Prices below are in USD per month.
| Plan | USD / month | Monthly credits |
|---|---|---|
| Hobby | $25 | 4,500 |
| Base | $100 | 60,000 |
| Starter | $200 | 180,000 |
| Growth | $500 | 650,000 |
| Pro | $750 | 1,250,000 |
Per-call credit costs: Core 8 · Markets 10 · Insights 12 · Transactions 15. Batch routes charge per wine or item. Monthly credits refill on renewal and unused monthly credits expire.
Pay as you go costs $6.50 per 1,000 credits without a subscription; purchased credits expire 12 months after the latest purchase. Per-product plans and enterprise arrangements are also available.
Confirm current allowances, billing rules and availability at API pricing and MCP pricing before quoting a plan.
API & AI integrations
Connect an AI assistant
The remote MCP server is https://chat.wine-labs.com/mcp. Use a client that supports remote MCP servers and OAuth, then sign in with a Wine Labs account. The setup guide includes instructions for Claude, Microsoft Copilot, Codex, Cursor and Windsurf.
Assistants can identify wines, retrieve market prices, compare offers, research auction and exchange activity, and support cellar valuation workflows. Available tools and data depend on account access and billing.
Build with the REST API
The public API base URL is https://external-api.wine-labs.com. Read the API documentation for endpoint inputs, authentication and responses.
- OpenAPI specification — endpoint definitions.
- MCP server card — server discovery.
- Agent skills index — integration resources.
- llms.txt — concise site index for AI tools.
- Full integration reference — tools, billing and request examples.
Customer examples
Published case studies describe how customers use Wine Labs data in their products and workflows:
- InVintory — catalogue matching and market pricing for collectors.
- The Duckhorn Portfolio — market presence and account planning in California.
- dVIN Labs — matching and pricing infrastructure behind Bacchus, its AI cellar assistant.
- WineFi — wine matching and market data for an investment platform.
Privacy & data handling
Refer to the privacy policy for personal data handling and the terms of service for permitted use. API and MCP integrations remain subject to authentication, account permissions and usage limits.
For AI workflows, obtain the user’s permission before uploading private inventories or changing account data. Keep credentials private and do not include them in citations. Contact Wine Labs for contractual, licensing or security requirements rather than inferring certifications from this overview.
Getting started
- Research a wine. Search the catalogue and compare available prices. Create an account for account features.
- Use an assistant. Follow the MCP setup guide and authorize a compatible client.
- Build an integration. Start with the API overview and endpoint reference.
- Discuss a business workflow. Contact the team about coverage, licensing or an enterprise use case.
Key terms
- Wine Labs ID
- The canonical wine identifier used by Wine Labs to connect records across data sources. It is cross-referenced to LWIN where one exists.
- LWIN
- Liv-ex Wine Identification Number, an industry wine identifier. A Wine Labs record does not require an LWIN to exist.
- Vintage & format
- The wine’s harvest year and bottle size or packaging. Both matter when comparing prices.
- Hammer price
- The winning auction bid before buyer’s premium and other applicable charges.
- Market price
- A price or estimate derived from observed market data. It is different from a guaranteed sale price.
- MCP
- Model Context Protocol: a way for compatible AI clients to connect to Wine Labs tools and retrieve data.
- Unified credits
- A shared usage wallet for supported REST API routes and MCP tools; call costs depend on the data family.