Auction lots
Every catalogue, ready to query
Each lot in the house — estimates, reserves, condition, provenance, consignor — exposed as one row your analyst or AI tool can filter, group, and forecast on.
Data domains
Beyond the catalogue PDF
The Lots domain captures everything the catalogue knows about a single lot, plus the operational metadata the catalogue hides — the reserve, the consignor link, the internal department category, the storage location, the marketing tier — all in one structured record.
Each lot links forward to bids, orders, and post-sale invoices, and backward to the consignor profile inside the Customer domain. That graph is what lets an AI tool answer 'which consignors had the highest sell-through in modern watches last year' in one hop.
Ask your data
From a question to an estimate-accuracy view
Ask how the catalogue performed against published estimates. The MCP server joins lots with their realised bids and returns a per-category accuracy view.
Access & governance
Reserves and consignor identity are protected
Catalogue-public fields (title, estimate, category) are openly readable. Reserve, consignor identity, and internal marketing tier are gated.
Reserves are masked from analyst roles by default and only revealed to finance, head-of-department, and the consignor's own dashboard.
Consignor-linked queries are subject to the same PII rules as the Customer domain.
Historical sold-lot data, including hammer and buyer paddle, is available without restriction to authenticated analysts.
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar