Beta

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

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

Market: bids and offers

Each wine's bids and offers on Cru World Wine together, grouped by wine (LWIN18). Offers are what a wine would cost to buy; bids what it could be sold for, net of Cru's commission. Either list is empty when that side has nothing. Prices are normal amounts in the market currency - 12345.5 is 12,345.50 - and every market states its currency.

READlist_marketLIVE
Needsmarket:readRESTGET /marketTry it
Reads, and changes nothing

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

Arguments

ALL OPTIONAL
ARGUMENTDESCRIPTION
lwin18array<string> · LWIN18 · ≤ 20 Only these wines, as 18-digit LWIN18 codes (wine, vintage and pack). Get them from search_wines.
depthinteger · ≥ 1 How many bids and how many offers to return per wine, best first. Omit for every level.
include_market_priceboolean Add Cru's market price for each wine. Default: false
include_last_tradeboolean Add the last traded price and date for each wine. Default: false
limitinteger · 1–50 Wines per page. Default: 10
offsetinteger · 0–10000 Wines to skip, for the next page. Default: 0

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

markets, by LWIN18, each with the wine, its bids and its offers — the same objects as list_bids and list_offers — and pagination.

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 Your portfolio

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).