Platform · API
For institutions that need the records to flow into their existing systems.
A museum lending department running its own collection management system. An estate attorney maintaining a parallel chain-of-custody record. An auction-house specialist building tools that read provenance research feeds. None of them want a second login; they want the records to appear inside the tools they already use.
Read. Write. Subscribe.
Pull records into the system that needs them
Authenticated requests return structured records — artworks, artists, exhibitions, provenance, attribution opinions, indicated market ranges — scoped to what the requesting party is permitted to see. Pagination, filtering, and field selection are standard. Source citations and dates accompany every record.
Example: GET /v1/artworks?artist=jacob-nuckols&include=provenance,custody
Submit records and updates back
Authorised parties can submit new records or update existing ones — a museum logging a loan, an attorney attaching an estate ruling, an authenticated dealer reporting a sale. Every write is signed, dated, and routed through the cross-validation rules before it lands. Writes that fail validation are returned with the specific rule that flagged them.
Example: POST /v1/custody-events
Be notified when something changes
Subscribe to event streams — provenance updates, sale events, attribution revisions, exhibition openings — and receive signed webhook deliveries when relevant changes occur. Retry semantics are at-least-once with idempotency keys. The receiving system stays in sync without polling.
Example: POST /v1/webhooks with events: ["provenance.updated","sale.closed"]
The API is gated, not hidden.
Access is granted by the data owner — a gallery, an estate, a collector — and recorded. A museum requesting read access to a collector's provenance records goes through the collector's approval; the architecture does not unilaterally open the records. Granted access is time-bounded by default and revocable at any time, with the revocation logged.
The full reference — endpoints, schemas, authentication, rate limits, versioning policy — is provided to qualifying clients. It is not posted on the public site because the surface is not the right entry point for most readers. If your situation calls for it, write to us and we will share the reference and a test environment.