Beta

The Partner Trading API v1 is in beta — endpoints and response shapes may still change.

Developers
Cru World Wine
API v1 · REST & MCP
Reference data

Search wines

Finds wines on Cru World Wine by name and returns their LWIN18 codes, which every other tool takes. Each result is one wine in one vintage and pack size, with its producer, region, product page, Cru market price, and its best 5 bids and best 5 offers (empty when there are none; get_wine has them all). It searches the way the Cru website's search does, best match first. Prices are normal amounts in the market currency - 12345.5 is 12,345.50 - and every market states its currency.

READsearch_winesLIVE
Needsmarket:readRESTGET /winesTry it
Reads, and changes nothing

Marked readOnlyHint, so an assistant may call it without asking the customer first.

Arguments

1 REQUIRED
ARGUMENTDESCRIPTION
querystring · 2–100 chars · required Words from the wine name, e.g. "Lafite" or "Petrus Pomerol".
vintageinteger · 1800–2100 Only this vintage year.
pack_sizestring Only this pack, written as bottles x size, e.g. "12x75cl" or "6x150cl".
limitinteger · 1–25 Most wines to return. Default: 10

Any other argument is refused with a tool error that lists what the tool accepts. Numbers may also be sent as strings, and booleans as "true" or 1.

Returns

STRUCTUREDCONTENT

wines (lwin18, wine_name, vintage, pack_size, producer, region, colour, product_url, market_price, and up to 5 bids and 5 offers, as list_bids and list_offers give them), currency, has_more.

The same object also comes as JSON text in content, for hosts that read only that.

Errors

A refusal — a wine that is not on Cru, a price out of range — comes back as a result with isError: true and a message worded for the assistant to act on. A connection without market:read is not offered this tool, and calling it anyway returns 403 with a JSON-RPC error naming the scope. Missing or invalid credentials return 401. Conventions every tool shares →

UP NEXT Wine details

API credentials

Enter the client key and secret issued by Cru. They are kept for this browser tab’s session — a reload keeps them, closing the tab or clearing them ends them.

Credentials are never included in copied examples, and are redacted from anything the console prints back.

Request API access

Tell us who you are and what you want to build. Cru issues a client key and secret for your organisation, scoped to what you need.

Markets you trade in (choose one or more)

We use what you send here to reply about API access, and for nothing else. Cloudflare Turnstile checks the form for bots (privacy policy).