Three learning paths into Provenance. Pick the track that matches what you're here to do — each step is self-contained, so you can stop after any one of them.
For vendors publishing their own posture for the first time
Sign up, publish your first trust page, embed the verify badge.
Step 1 · 5 min
Quickstart
Six steps from signup to embedding the verify badge — about 5 minutes.
Read →Step 2 · 6 min
Trust pages
Full publish flow: drafts, statements, evidence, subprocessors, custom domain.
Read →Step 3 · 3 min
Verify badge
One HTML snippet you embed in email signatures, MSAs, README files, sales decks.
Read →For engineers integrating Provenance into a procurement, GRC, or trust workflow
Read the public directory, drive vendor picks programmatically, subscribe to changes.
Step 1 · 8 min
HTTP API explorer
Interactive OpenAPI explorer — try every public + authenticated read endpoint live.
Read →Step 2 · 5 min
Webhooks
SVIX-signed events for evidence + statement changes. Per-customer Svix portal.
Read →Step 3 · 4 min
Billing & Stripe
Self-serve checkout flow + Stripe Customer Portal + the three billing endpoints.
Read →For compliance, legal, and security teams owning AI / privacy / security disclosures
Ship Article 50 disclosures and machine-readable provenance metadata before 2 August 2026.
Step 1 · 9 min
EU AI Act Article 50
Four transparency tracks + Code of Practice references + JSON-LD machine-readable mark.
Read →Step 2 · 6 min
Trust pages
Same workflow your security/privacy/AI disclosures land in — one page, one source of truth.
Read →Step 3 · 8 min
HTTP API explorer
Programmatically read disclosures + evidence for downstream compliance tooling.
Read →Looking for something else? Check the FAQ, the changelog, or email us.