# Brilliant Colors Inc

Brilliant Colors Inc is a direct importer of fine colored gemstones, including sapphire, ruby, emerald, paraiba, padparadscha, spinel, garnet, beryl, aquamarine and other rare gemstones.

## Primary URLs

- [Homepage](https://www.brilliantcolorsinc.com/)
- [Catalog](https://www.brilliantcolorsinc.com/Catalog)
- [Plain catalog index for crawlers and AI](https://www.brilliantcolorsinc.com/Catalog/Index)
- Gemstone listing URLs use the pattern `/Catalog/{sku}`.
- [Shows](https://www.brilliantcolorsinc.com/Shows)
- [Contact](https://www.brilliantcolorsinc.com/Contact)
- [XML sitemap](https://www.brilliantcolorsinc.com/sitemap.xml)
- [Machine-readable catalog feed](https://www.brilliantcolorsinc.com/catalog-feed.json)
- [Robots policy](https://www.brilliantcolorsinc.com/robots.txt)

## Catalog Data

Each public gemstone listing has a stable URL using its item number or public SKU. Listing pages may include gemstone type, color, shape, weight, dimensions, treatment, laboratory/certificate information, image, video availability and contact paths for sourcing assistance.

Public catalog listings are exposed through the XML sitemap, the plain server-rendered catalog index and the machine-readable catalog feed. Gemstone images are included in the image sitemap data and catalog feed when available as real image files.

## AI And Search Crawling

Brilliant Colors Inc allows major search and AI discovery crawlers in robots.txt, including Googlebot, Googlebot-Image, bingbot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, GPTBot, Google-Extended and CCBot.

## Contact

For sourcing, inventory and gemstone availability questions, use https://www.brilliantcolorsinc.com/Contact or email Info@BrilliantColorsInc.com.

## Current Inventory Search

### Filtered catalog pages

Filtered catalog pages contain current matching listings and product links in server-rendered HTML, without requiring JavaScript to read the initial results. Customers can adjust the filters interactively. Catalog searches show available listings of at least 1 ct; the API's supported weight range is separate.

- [Available blue sapphires](https://www.brilliantcolorsinc.com/Catalog/Filtered?type=sapphire&color=blue&sort=carat-asc)
- [Available pink sapphires](https://www.brilliantcolorsinc.com/Catalog/Filtered?type=sapphire&color=pink&sort=carat-asc)
- [Available yellow sapphires](https://www.brilliantcolorsinc.com/Catalog/Filtered?type=sapphire&color=yellow&sort=carat-asc)
- [Available rubies](https://www.brilliantcolorsinc.com/Catalog/Filtered?type=ruby&sort=carat-asc)

The HTML search route is `/Catalog/Filtered`. Query parameters use standard `name=value` pairs separated by `&`. Canonical URLs use lowercase readable values and hyphenated parameter names. Older inventory codes remain accepted and redirect to the readable URL.

Supported HTML parameters include `type`, `color`, `shapes`, `matching`, `min-carat`, `max-carat`, `min-length`, `max-length`, `min-width`, `max-width`, `treatment`, `origin`, `laboratory`, `certification`, `item-number` and `sort`. `item-number` searches by item-number prefix; `/Catalog/{sku}` opens an exact item. Multiple shapes, colors or treatments use comma-separated values. Examples are `type=sapphire`, `color=blue`, `shapes=oval`, `treatment=heated` or `treatment=untreated`.

Use `matching=single` for individual stones and `matching=pair` for matching pairs. Omitting matching includes both. Minimum and maximum values are inclusive. Length is the longer face-up axis and width the shorter, in millimeters. Carat weight for pairs is combined. Do not widen a customer's requested tolerances. A dimensional match does not guarantee physical fit.

Example: single oval blue sapphires, length 7.8–8.5 mm and width 5.8–6.5 mm, heaviest first:

https://www.brilliantcolorsinc.com/Catalog/Filtered?type=sapphire&color=blue&shapes=oval&matching=single&min-length=7.8&max-length=8.5&min-width=5.8&max-width=6.5&sort=carat-desc

`sort=carat-asc` is lightest first; `sort=carat-desc` is heaviest first. Public prices are not displayed. Page numbers are not part of shared HTML URLs. The initial HTML may contain only the first results page; do not describe it as the complete inventory if more results remain. The interactive catalog loads further results; a non-JavaScript Next button submits pagination separately. The public API below supports explicit pagination for a complete search.

### Structured inventory API

- [Public inventory API](https://www.brilliantcolorsinc.com/inventory-api.php)
- [Inventory API specification](https://www.brilliantcolorsinc.com/inventory-openapi.json)

The API supports current website inventory searches by gemstone type, color, shape, carat range, dimensions in MM, treatment, pair/single matching and sorting; individual records can be retrieved by public SKU. Public prices are not provided.

For a single-stone mounting, use matching=single. Dimension ranges are inclusive: length is the longer face-up axis and width the shorter, allowing rotated measurements. Use the customer's specified tolerances; dimensional matches are candidates, not a guarantee of physical fit. Carat weight for pairs is the combined pair weight.

Available inventory is the default. Follow has_more and next_offset when a complete result set is required. When no laboratory is recorded, the website and API certification.label display "Not Certified" under the catalog business convention; the API retains certification.status="unknown" and laboratories=[]. When laboratories are recorded, certification.label contains their normalized names and certification.status="recorded". Laboratory records are separate from certificate-file availability: a recorded laboratory remains recorded while its physical certificate is awaiting delivery, scanning or linking to the SKU. These labels describe catalog records, not independent verification of certification. checked_at is the API query time, not the inventory synchronization time. Search snippets can be older than the live record; check availability on the product page or API.
The catalog feed also supplies is_pair (true, false, or null when unknown), weight_basis (combined_pair, listing, or unknown), and dimensions_mm with numeric recorded length and width. Missing dimensions are null. For mounting comparisons use the longer and shorter axes rather than assuming recorded orientation. Legacy dimension labels may be rounded; use numeric dimensions_mm for exact range comparisons.

Sapphire searches include Padparadscha inventory. With type=sapphire, color=peach searches both peach sapphires and Padparadscha records, including Padparadscha recorded under other colors. Without Sapphire selected, Peach remains an ordinary color filter. Individual records retain their original classification. API type=padparadscha remains an exact classification search; legacy HTML Padparadscha collection links redirect to the combined Sapphire/Peach collection.

### API search workflow and examples

The [OpenAPI specification](https://www.brilliantcolorsinc.com/inventory-openapi.json) is the authoritative parameter and response reference. API parameter names use underscores (for example min_length_mm); the HTML catalog uses different, hyphenated parameter names. Do not mix the two URL formats.

Example request: available single blue sapphires, oval or cushion, no heat, 2.99–4.00 ct, length 10–11 mm and width 8–9 mm. Bounds are inclusive and apply to both shapes in this example. This is a request example, not a promise of current stock:

https://www.brilliantcolorsinc.com/inventory-api.php?type=SA&color=BL&shapes=OV,CU&treatment=N&matching=single&min_carat=2.99&max_carat=4&min_length_mm=10&max_length_mm=11&min_width_mm=8&max_width_mm=9&availability=available&sort=carat_asc&limit=1&offset=0

1. Apply every requested constraint together. Comma-separated shapes mean alternatives within the shape filter. Do not silently widen the customer's limits. Clarify ambiguous requirements before selecting filters.
2. Read items from a successful response. An empty items array means no exact matches at query time. Any relaxed search must be identified as alternatives, with the differing requirements disclosed.
3. This example uses limit=1 to demonstrate pagination. If has_more is true, replace offset with the returned next_offset and keep every other filter unchanged. Continue until has_more is false. For normal searches use up to limit=50. Deduplicate by sku if inventory changes during pagination.
4. Recheck a selected record with sku alone, for example https://www.brilliantcolorsinc.com/inventory-api.php?sku=7144 . Detail returns item; search returns items. Example SKUs can become unavailable or return 404. Check availability again and link using the returned url for that gemstone.
5. Use certification.label for Not Certified or recorded laboratory names. A recorded laboratory does not imply a certificate file has been published. Public prices are hidden; do not invent prices.
6. An HTTP error is not evidence of no matching stock. For 429 or 503, respect Retry-After and report temporary unavailability if the request cannot be completed. checked_at identifies query time, not inventory synchronization time.