CARDINALStart with the public contract
The canonical API base is https://cardinalsilicon.com/api/v1. Public endpoints do not require an API key.
Use OpenAPI for exact request fields, response schemas and status codes. Use llms.txt for agent discovery and links to machine-readable content.
Read the quickstart ↗Available endpoints
| Method | Path | Purpose |
|---|---|---|
GET | /api/v1/catalog | Read the eight-model sourcing catalog |
GET | /api/v1/catalog/{variantId} | Read an exact variant, including educational references |
GET | /api/v1/documents | Read manufacturer-source records |
GET | /api/v1/documents/{documentId} | Read one manufacturer-source record |
GET | /api/v1/articles | Read the published guide index |
GET | /api/v1/health | Check site and request-service readiness |
POST | /api/v1/estimate | Calculate a memory estimate from explicit assumptions |
POST | /api/v1/requests | Submit a real buying or selling inquiry |
The request sandbox adds a validation-only endpoint at /api/v1/sandbox/requests. It never creates an inquiry or sends email.
Keep evidence attached to the answer
Catalog records separate models from exact variants. Preserve variant identifiers, source identifiers, dates and specification conditions when presenting an answer.
The listing reflects our sourcing scope. An exact-variant reference can describe hardware outside that scope. A technical reference does not establish current stock or pricing.
Published compute figures describe manufacturer peaks. Memory estimates do not establish server compatibility, application quality or throughput. Null values mean unknown or unpublished information.
Use the interface that fits your application
Download the Cardinal Silicon CLI package. Follow the included README for commands. The package is not yet published to a package registry.
npm install -g https://cardinalsilicon.com/downloads/cardinal-silicon-cli-0.1.0.tgzPublic pages also support Accept: text/markdown. The HTTP API and OpenAPI contract are the supported integration surfaces; no MCP server is published.
Separate testing from real sourcing
Test request payloads in the sandbox first. Submit to /api/v1/requests only when the buyer authorizes a real inquiry.
Read authentication and request controls before implementing retries. Read the versioning policy before depending on response fields.