Reference
How the lab-grown market gets normalized.
A short reference for the trade: how StoneOS turns dozens of supplier feeds into one comparable dataset, and the metrics that make price discovery possible.
The 4 Cs, as a canonical schema
Every supplier describes stones differently. We map all of it onto one vocabulary so a 1.50ct F/VS1 from one supplier is directly comparable to the same spec from another.
Cut
Stored as a canonical grade (Ideal → Fair). We map each supplier's cut nomenclature onto this scale so listings are comparable.
Color
D–Z, normalized per stone. Cross-supplier comparison only compares like-for-like color.
Clarity
FL → SI, canonicalized. Mixed supplier abbreviations resolve to one vocabulary.
Carat
Exact weight; price-per-carat ($/ct) is derived for normalized comparison across sizes.
Price-discovery metrics
Best price
The lowest supplier price for an exact 4C spec, surfaced by /v1/diamonds/compare.
Spread
The gap between the highest and lowest price for the same spec — a read on how fragmented that spec is.
Median $/ct
The middle price-per-carat across suppliers for a spec — a robust mid-market reference where no index exists.
Certificates
Listings carry their lab and report number (IGI, GIA, GCAL). The certificate reference travels with the stone through the API and into sourcing, so what you quote is what you receive.
Common questions
- How is inventory normalized?
- Each supplier's CSV/API feed is mapped into one canonical schema (4 Cs, certificate, measurements, price in cents). Invalid rows are skipped and logged; prices convert to integer cents.
- How fresh is the data?
- Each ingestion run stamps listings with a run id and last-seen time. Stones not present in the latest run are reconciled to unavailable, so the market reflects current supply.
- Is this natural or lab-grown?
- Lab-grown only. Natural diamonds already have an established benchmark; lab-grown pricing is fragmented and unindexed, which is where aggregation creates the most value.
- How do I access it?
- Through the JSON API (keyed, metered, tier-gated) or the web terminal. Build your own storefront, pricing tool, or procurement on top.