For institutions

Collection accountability, loans, and public verification APIs

Align curatorial records with a modern certificate registry, immutable event logs, and partner-ready verification endpoints.

  • Append-only asset events across departments for transparent custody and movement history.
  • Globally unique certificate numbers with versioning and verification scores for partner lookups.
  • API keys with scopes and per-planet rate limits for integrations and donor reporting.
Subscribe

Early proof & previews

We are shipping evidence as fast as we ship code—placeholders mark what is coming next.

Architecture

Event ledger

Public read on asset_events for transparency; authenticated inserts only—no silent edits.

Data model

Certificates table

Unified certificate registry spanning art, collectibles, vehicles, and real property verticals.

Roadmap

API surface

Key management exists in-database; HTTP verification routes ship next on your timeline.

“We are evaluating Provenance where our TMS ends and public trust begins—especially for traveling exhibitions.”

Registrar office, permission pending

Testimonial in progress — NDAs in review.

Common questions

What does an append-only asset event log provide?

Each mutation emits a transparent record with actor, payload, and timestamp—ideal for custody transfers, loans, and cross-department accountability.

Are certificate numbers globally unique?

The unified certificates table issues numbers that are unique across asset planets so partners can verify without guessing which silo to query.

How mature is the HTTP verification API?

API key storage, scopes, and rate limits exist in the database today; wire your preferred edge or service layer to expose partner endpoints when you are ready.

Main marketing site