/artworks
Browse the public rights-cleared artwork catalog.
Access the public catalog, canonical registry evidence, rights-aware observed market facts, comparable sales, immutable artist indices, research valuation and audited exports through one versioned contract.
Start with the public status endpoint, then move to scoped bearer access.
Read status and OpenAPI without a key.
Create an API client inside an organization workspace.
Usage is metered only after auth and scope checks pass.
curl --request GET \
'https://relict.cloud/api/v1/status' \
--header 'Accept: application/json'{
"product": "RELICT API",
"version": "1.3.16",
"status": "operational",
"as_of": "<UTC timestamp>"
}Commercial registry and intelligence routes use a bearer key with explicit scopes.
curl --request GET \
'https://relict.cloud/api/v1/registry/search?q=monet' \
--header 'Authorization: Bearer relict_live_…' \
--header 'Accept: application/json'Server-side storage keeps hashes, not retrievable cleartext keys. Unauthorized and scope-denied requests are rejected before endpoint Units are charged.
These routes are taken from the current `/api/v1` contract — no placeholder `/advisor` or `/valuations` endpoints.
Browse the public rights-cleared artwork catalog.
Search canonical registry records with scoped API access.
Read field-level source, confidence and rights evidence.
Observed sale facts available to the caller’s entitlement boundary.
Rank comparable observed sales without turning the score into a valuation.
Read immutable artist-index builds and evidence.
Run research/demo valuation with explicit evidence and cannot-value states.
Create rights-aware audited exports for entitled clients.
No fictional npm/Python package names.
Generate a typed client with the tooling your stack already trusts.
https://relict.cloud/api/v1/openapi.jsonNo official RELICT SDK package is published in this release. The API contract is the canonical integration surface.
contract: v1.3.16Configured per organization API client.
Weighted endpoint usage from the current runtime configuration.
1 unit per accepted request.
1 unit per accepted request.
1 unit per accepted request.
2 units per accepted request.
3 units per accepted request.
4 units per accepted request.
5 units per accepted request.
8 units per accepted request.
10 units per accepted request.
1 unit per accepted request.
1 unit per accepted request.
2 units per accepted request.
10 units per accepted request.
20 units per accepted request.
Public, research and licensed-commercial facts remain separated by data-use policy. Observed sale facts stay distinct from modeled estimates and artist indices, with source, as-of, confidence and methodology evidence where the contract exposes them.