Reaching CultX portfolios, the order book and on-chain settlement

An order book that lists every active bid and offer across all case sizes, a stated £200m pool of investment-grade bottles, and roughly 200,000 global prices refreshed daily — those are the numbers Cult Wines puts on CultX, and they are what a single account sits on top of. The bottles themselves live in a bonded warehouse in the holder's name; the prices come from a Wine-Searcher partnership; settlement is written to the Algorand public ledger so ownership transfers the moment a trade clears. For anyone who wants those holdings, trades and marks out of the app and into their own systems, the data is structured and account-scoped — the work is reaching it under the holder's authorization and turning it into a typed feed.

The bottom line is short. CultX is a trading venue with a real per-user record behind it: what you hold, where it's bonded, what you've bid, what cleared, and what it's worth today. We map the authenticated session a member uses, document the endpoints behind the order book, portfolio and valuation views, and hand back a client that pulls the same data on a schedule. Because settlement rides Algorand, transfer events are also legible on a public chain — a useful corroboration layer, not the whole picture.

What a CultX account actually holds

Each row below is a surface the app exposes to a logged-in member, named the way CultX names it where the listing and its help articles let me. Granularity is what an integrator can expect to read per record.

Reading the order book and a holdings call

A worked sketch of the session a CultX member drives, so the shape is concrete. Endpoint paths and field names here are illustrative — the exact ones get confirmed and pinned during the build, against a consenting account. The pattern is a bearer token from login, then reads keyed on a fine-wine identifier (LWIN is the standard reference for fine wine) and on the member's own portfolio.

# Illustrative session — paths/fields confirmed during the build, not published by CultX

POST /auth/token            # email + password -> bearer (JWT) + refresh token
GET  /markets/{lwin}/orderbook   # active bids + offers across every case size
GET  /portfolio/holdings    # cases held, bonded location, book cost
GET  /portfolio/valuation   # mark vs Wine-Searcher + Cult Wines Global Index

# GET /markets/{lwin}/orderbook  ->
{
  "wine": "Chateau Margaux",
  "vintage": 2015,
  "unit": "OWC 1x6",            # case size matters: a price is meaningless without it
  "bids":   [ {"price": 3120, "qty": 2}, {"price": 3080, "qty": 1} ],
  "offers": [ {"price": 3260, "qty": 1} ],
  "last_trade": { "price": 3180, "ts": "2026-06-09T11:04:22Z" },
  "cultx_liquidity": 4,         # 1..5, how findable the wine is globally
  "spread_pct": 4.5
}

# client handles: 401 -> refresh token; 429 -> back off; case-size axis kept explicit

What the build hands over

Everything below is scoped to the surfaces above, not a generic kit.

• An OpenAPI / Swagger spec covering the login, order-book, holdings and valuation calls, with the case-size axis modelled as a first-class field.
• A protocol and auth-flow report: the bearer/JWT and refresh-token chain as captured, plus how the app keys requests on wine identity and case size.
• Runnable source for the key endpoints in Python and Node.js — order book, holdings, valuation, trade history — with retry and token-refresh built in.
• Automated tests with recorded fixtures, including the awkward cases: multiple case sizes for one wine, bonded versus delivered stock.
• Interface documentation: the wine-identity mapping (LWIN, vintage, producer), what the 1–5 CultX Liquidity score means, and how valuations tie to Wine-Searcher and the Cult Wines Index.
• Compliance and retention guidance — consent records, logging, and data minimization under UK data-protection law.

Authorized ways into the data

Interface integration of the member session

The workhorse. We capture the authenticated traffic a consenting member generates, map the endpoints behind the order book, portfolio and valuation views, and build a typed client over them. Reachable: holdings, own orders, trades, marks, reference data. Effort is moderate; durability is good as long as a check flags front-end changes. Access is arranged with the client during onboarding — a consenting account, no customer paperwork wall.

User-consented credential access

For a product that needs to read a specific member's data on their behalf, we run the integration under their login with scoped, server-side tokens and a clear consent record. This is the basis the rest of the work rides on, given fine wine sits outside any open-banking regime.

On-chain settlement reads

Because trades settle on Algorand, transfer and settlement events are queryable from the public ledger through an Algorand indexer. Reachable: timing and provenance of transfers; not the named-account, bonded-location detail. We use it to corroborate the interface data, not to stand alone.

Native export, where present

If the member-facing portal offers a statement or holdings export, we take it as a low-effort baseline and reconcile it against the live reads.

For most CultX work the session integration is what we actually recommend, run on a consenting member's authorization, with the Algorand reads bolted on where provenance matters and an export used to cross-check holdings. That ordering follows the data: the per-account detail only exists inside the authenticated session.

Where the data-protection line sits

Fine wine investment is not an FCA-regulated activity in the UK — the regulator's own warnings about unregulated investments spell out that buyers fall outside the Financial Services Compensation Scheme and the Ombudsman. That matters for the integration because there is no AIS or open-banking regime to consent through here. The dependable basis is the account holder's own authorization to read their data. Personal data in scope is governed by UK GDPR and the Data Protection Act 2018: we keep consent scoped to the surfaces a client actually needs, honour revocation by tearing down tokens and stopping pulls, minimize what we store, and log access. Where a client needs it, the work runs under NDA. Nothing here touches another member's records.

Things the build has to get right for CultX

These are the parts that trip up a naive port, and the parts we handle.

• The case-size axis. One wine trades in several formats — a 1×6 owned case, a 1×12, magnums — each with its own bid, offer and price. We model case size as a first-class key so a "price" is never ambiguous and bids reconcile to the right unit.
• Bonded versus delivered stock. A case in the bonded, duty-suspended warehouse is a different asset, tax-wise, from one delivered to a personal cellar. We track that state so valuations and any downstream tax treatment line up with reality.
• Wine identity that joins outward. CultX marks against Wine-Searcher and the Cult Wines Index, so holdings have to map to a stable wine key. We normalize on LWIN, vintage and producer so a CultX position can be matched to external pricing and indices without guesswork.

Where CultX data tends to go

• A wealth platform folding a client's wine holdings into a single net-worth view, marked once a day against the valuation feed.
• An accounting workflow pulling executed trades as dated lots with price, so a collection's gains are reportable.
• A market desk watching spreads and the CultX Liquidity score across a watchlist to flag entry and exit points.

Keeping prices and positions current

Two cadences, matched to how CultX itself updates. The roughly 200,000 daily global prices and portfolio valuations fit a once-a-day snapshot. The order book and a member's own bids and offers move in real time, so those are polled on events or short intervals. A backfill job replays history into the store on first sync, and the client handles token refresh, rate limits and back-off so a long-running pull does not stall silently.

Screens we mapped

Store screenshots used while sketching the surfaces above. Select one to enlarge.

Sources checked, and when

Mapped from the Cult Wines launch announcement, Wine-Searcher's account of the partnership and data scope, the FCA's position on unregulated investments, and CultX's own how-to material on the order book and trading surfaces — read June 2026 and cross-checked against the Play and App Store listings.

• Cult Wines launches CultX, powered by Wine-Searcher (PR Newswire)
• Wine-Searcher: powering the CultX platform
• CultX: how to use the order book and trading tools
• FCA: high-risk investments from unregulated firms

Mapped by the OpenBanking Studio integration desk · June 2026.

Other platforms in the same wine-data space

Neighbouring services an integrator runs into when consolidating fine-wine positions. Listed for context, not ranked.

• Liv-ex — the trade exchange and price benchmark; member firms hold transaction and reference data that any wine valuation leans on.
• Vinovest — AI-managed wine and spirits portfolios; holds per-account positions and managed valuations.
• Vindome — a live marketplace with no minimums; carries member listings, bids and a portfolio record.
• Alti Wine Exchange — blockchain-based bottle offerings; ownership and trade records sit partly on-chain, like CultX.
• Vint — securitized wine and spirits collections; holds investor positions in managed offerings.
• WineFi — a UK syndicate model for fine-wine investing; holds member stakes and syndicate-level holdings.
• WineOwners — portfolio management and a marketplace; stores cellar inventory, valuations and trades.
• BlockBar — tokenized wine and spirits with NFT-backed ownership; transfer records live on-chain.
• WineCap — fine-wine investment with data-led analytics; holds client portfolios and market data.

Questions integrators ask about CultX

Which CultX surfaces carry the per-account data — holdings, bids, valuations?

Three places. Your portfolio view holds the cases you own with their bonded location and book cost; the order book and your own active bids and offers sit on the trading side; the valuation engine marks each wine against Wine-Searcher pricing and the Cult Wines Global Index. A build reads all three behind one authenticated session and joins them on a stable wine key.

Does CultX recording trades on Algorand mean ownership is just readable on-chain?

Only partly. Settlement and transfer events are written to Algorand's public ledger and corroborate provenance and timing, which is useful as a second source. But mapping a ledger entry back to a named account, a case size and a bonded location still needs the authenticated app session, so the chain supplements the interface route rather than replacing it.

Fine wine is not FCA-regulated, so what governs the data side of a CultX integration?

The trading product is outside FCA scope, as the regulator's own warnings about unregulated investments make clear. The data side is governed by UK GDPR and the Data Protection Act 2018, and the dependable basis for access is the account holder's own authorization. We run consented, logged, data-minimized, under NDA where a client needs it.

Can a sync keep up with a 24/7 order book and a daily price refresh?

Yes, with two cadences. Valuations and the roughly 200,000 daily global prices fit a once-a-day snapshot, while the order book and your live bids and offers are polled on events or short intervals so spreads and fills stay current. Token refresh, rate limits and back-off are handled in the client we ship.

Engagement

Source code for the CultX client lands runnable, and you pay from $300 only once it's delivered and you're satisfied with it; prefer not to host anything yourself, and the same order-book, holdings and valuation calls run as a pay-per-call hosted API with no upfront fee. Either way the build runs in one to two weeks. Tell us the app name and what you want out of its data, and we arrange access and the rest — start at /contact.html.