The geology, slope, elevation, and classification of 4,925 vineyard sites across Burgundy, Champagne, the Northern Rhône, and Bordeaux — structured, scored, and queryable via API. The first terroir intelligence platform ever built. Nothing else like it exists.
A Premier Cru vineyard in Gevrey-Chambertin called Les Champeaux physically borders the Grand Cru Chambertin. Zero metres of separation. Same limestone. Same slope. Same elevation band. The geology is continuous.
The price difference? 10×.
This pattern repeats across every wine region we've mapped. The API surfaces every gap — spatial proximity, geological continuity, topographic alignment, producer depth. The dataset that lets you build products the wine world has never seen.
{
"climat": "Les Champeaux",
"classification": "premier_cru",
"nearby_grand_crus": [{
"name": "Chambertin",
"distance_metres": 0
}],
"geological_match": true,
"elevation_metres": 301.5,
"slope_degrees": 6.6
}This vineyard borders Chambertin at 0 metres on identical geology. Classified Premier Cru. The API knows this for every plot in Burgundy.
We didn't build this data to confirm what the wine world already believes. We built it to test it. Here's what we found.
No gap. No geological break. The same formation runs under both classifications. The boundary is legal, not geological. The price ratio between them can exceed 10 to 1.
The big houses source fruit from Grand Cru villages and add blending, ageing, and brand. The growers farm the same classified ground. The price difference between them is the brand, not the terroir.
Cretaceous chalk in Champagne. Jurassic limestone in Burgundy. Palaeozoic granite in the Rhône. Formations separated by hundreds of millions of years of geological history, processed and scored by a single intelligence system.
In Gevrey-Chambertin, the Grand Crus sit between 260m and 300m on the slope. Several Premier Crus and even village-level vineyards occupy the same band — same altitude, same exposure, dramatically different classification and price.
This is the kind of pattern that's invisible on a wine list but obvious in the data.
These are the patterns that are invisible on a wine list, obvious in the data, and now queryable via API.
Proven across formations separated by hundreds of millions of years. The engine processes any terroir. That's why it scales.
The engine has been proven across four fundamentally different terroir types. Extending it to new regions is an operational question, not a technical one.
One integration covers every region. Consistent structure, consistent quality. New regions inherit the same schema automatically.
{
"climat": "Les Champeaux",
"classification": "premier_cru",
"gc_distance_m": 0,
"geological_match": true,
"elevation_m": 301.5,
"slope_deg": 6.6
}{
"village": "Ambonnay",
"classification": "grand_cru",
"echelle": 100,
"cote": "Montagne de Reims",
"terroir_score": 8.7
}{
"lieu_dit": "Les Bessards",
"appellation": "Hermitage",
"elevation_m": 265,
"aspect": "south",
"slope_deg": 22.4
}{
"terroir_zone": "Pauillac-North",
"appellation": "Pauillac",
"geology": "High terrace gravel",
"terroir_score": 8.7
}These features require spatial terroir data. Until now, that data didn't exist in structured form. Now it's an API call.
Your wine e-commerce shows appellation, vintage, price. With one API call, add the geology, the Grand Cru proximity, the slope profile. Context that gives every bottle a story — and gives your customer a reason to buy it.
← 1 API call
Most wine recommendations use collaborative filtering. With Vintelligence, recommend by terroir: continuous geology, shared slope band, the same conditions that produce the wine someone already loves — at a different price point.
← terroir similarity query
Native MCP integration means any AI assistant can query 4,852 vineyard sites with structured terroir data. When a user asks for a recommendation, your AI responds with geological evidence — not pattern-matched guesswork. Already powering Claude by Anthropic.
← MCP tool call → structured terroir response
Free tier: 25 calls/day across all regions. No credit card. No approval process. No time limit. You'll have a working key in thirty seconds.
REST endpoints for appellations, geology, producers, and spatial proximity. One key covers every region. Typed responses, consistent schema.
MCP-native for AI assistants. Standard REST for everything else. Full documentation with working examples for every endpoint.
Every tier includes every region. Never charged separately. New regions added to your existing key at no extra cost.
4,925 vineyard sites. Four wine regions. 873 appellations with intelligence. Free tier starts now.
Enterprise or custom integration? Get in touch