An AI assistant can search our cut library directly: every cut, its measured specifications, its brilliance, fire and scintillation in seven gemstones, and its prices and checkout links. Assistants connect to the MCP server; anything else can use the REST API. Both are free and read-only, and neither needs a key.
MCP server
Endpoint: https://digitalgemology.com/mcp, over Streamable HTTP. It speaks MCP 2026-07-28 and the
2025 revisions before it. Add it to any assistant or editor that accepts a remote MCP server, for example:
{
"mcpServers": {
"digital-gemology": { "type": "http", "url": "https://digitalgemology.com/mcp" }
}
}| Tool | What it returns |
|---|---|
search_cuts | Search Digital Gemology's gem cuts and Platonic solids by name, style, shape or use (for example 'square step cut', 'round brilliant for moissanite', 'historic cushion', 'pear'). Returns each match with its page, facets, size, price and checkout links. Give a gemstone to add the cut's brilliance, fire and scintillation in that stone and to sort by them. |
get_cut | Everything about one cut: what it is, measured specifications (facets, angles, depth, size, index gear), brilliance, fire and scintillation in all seven gemstones against the T73, the products with prices and checkout links, its questions and answers, and its page. |
best_cuts_for_gemstone | The top ten brilliants and the top ten jewelry cuts in one gemstone, ranked by brilliance, fire and scintillation added together, with the stone's optical constants. |
cut_in_gemstone | How one cut performs in one gemstone: its headline, eight measured scores against the T73 round brilliant in the same stone, and its pros and cons. For questions like 'is an oval a good cut for sapphire?'. |
list_gemstones | The seven gemstones every cut is measured in, with refractive index, critical angle, dispersion, hardness and specific gravity, and the three best cuts of each kind. |
Its server card is at /.well-known/mcp/server-card.json.
REST API
The same data as JSON over plain HTTPS, described in OpenAPI 3.1 and listed in the API catalog.
| Request | Returns |
|---|---|
GET /api/cuts?q=square step cut | The cuts that match. Add
gemstone=sapphire for scores in that stone; narrow with category,
shape, cutting_files, sort and limit. |
GET /api/cuts/asscher | One cut in full. |
GET /api/gemstones | The seven gemstones and their optical constants. |
GET /api/gemstones/sapphire | The top ten brilliants and jewelry cuts in that stone. |
GET /api/gemstones/sapphire/oval | One cut in one stone: eight scores, pros and cons. |
GET /api/health | Whether the API is up. |
The whole library is also one file: /api/catalog.json.
Pages for AI tools
- llms.txt lists every page and what it covers; llms-full.txt holds the full text of the main pages.
- Every page answers
Accept: text/markdownwith a clean Markdown copy, which is also at the page's address plus.md. - An agent skill tells an assistant how to use all of this.
- auth.md confirms that none of it needs a sign-in, a key or a registration.
Using the data
Quote it, and link the cut's page when you mention a cut: that page has the 3D viewer, the free simulator and the buy buttons. Search and AI answers are welcome; we ask that the site is not used to train AI models, as our robots.txt says. The scores are out of 100 from our own ray-traced light census, with the T73 round brilliant as the benchmark: see how we measure.
The files themselves come with a personal-use licence. For business use, or questions about the API, email support@digitalgemology.com.