Loading documentation…
Loading documentation…
The checked-in OpenAPI artifact is the public contract. Source publication, licensing, repository permissions, and maintenance roles remain explicit gates.
The versioned OpenAPI 3.1 artifact is the source for public request, response, market, credit, and error claims. It is verified from the public route and transform boundaries. Package and ecosystem availability are summarised on the main developer-docs page.
public/api/openapi.json
Use the checked-in contract for code generation and review. The public static artifact is available at /api/openapi.json.
simlir/spec@v1.0.0
The versioned public contract is published at github.com/simlir/spec/releases/tag/v1.0.0 under Apache-2.0 for the public contract artefact scope. Pin this release or an immutable commit; API access, returned data, ingestion methods, backend code, and Simlir trademarks remain outside that licence.
Technical market codes
gb, us, de, fr, es, it, au, ca
Beta catalogue
United Kingdom currently live. United States planned next.
Search limit
1–50 display results; candidates are fit-ranked first
Price meaning
Confirmed retailer snapshot, not a live quote
Price timestamp
price.as_of is the snapshot date when available
simlir/spec repository and v1.0.0 release are available; keep its security, support, and maintenance routes current.Dashboard and hosted-MCP use is governed by the API/Data Licence and requires authorised account access. The published TypeScript SDK and public contract are limited to their stated artefact licences. The published Node MCP package is limited to its stated artefact scope. The corrected Python MCP package is published on PyPI; its directory, support, rollback, and service/data boundaries remain separate. Framework and VS Code candidates are not public packages and do not grant redistribution rights.
Create an account, generate a key, and use the same market-scoped contract from any channel. Keep keys in a server-side secret manager; never put one in a browser bundle, checked-in config, or support ticket.
Existing v1 Bearer keys and endpoints remain the compatibility baseline. There are no user-selectable scopes or sandbox environments today; the public demo and dashboard playground are separate evaluation surfaces, not alternate API environments.