PERMISYN
Public transparency log · live

The record we cannot edit,
and you do not have to believe.

Every attestation Permisyn issues — each governed call, each permission change, each agent let in from another company — is written into an append-only Merkle log whose roots are stamped into Bitcoin. Below, that log verifies itself: we hand your browser the hashes and your browser does the arithmetic. If we invented any of them, the check fails in front of you.

Entries logged
signed, append-only
Anchors sealed
hash-chained to each other
Latest Bitcoin block
awaiting the next confirmation

reading the tree head…

01Check it yourself

Verify a record without trusting us

Paste anything this log covers. We serve the leaf, its sibling path and the published root; your browser re-hashes the entry's own contents, folds it up the tree, and compares. Five separate questions get five separate answers, because a single tick would hide which one is missing — and the fifth is the one we cannot answer for you, because it is checked against a head your browser wrote down before this visit.

Verify a recordruns in your browser · no account, no key
Which id resolves
A proxied runrun_proxy_…the run id as the dashboard shows it
A passport revisionprev_…the revision id, not the agent id
A cross-org visaxvisa_…:grantedsuffixed :granted or :refused
Cross-org termsxtrust_…:registeredsuffixed :registered
02Anchored to Bitcoin

A date nobody can move, including us

A signature proves who attested, never when — the key holder can sign any date they like, and that includes Permisyn. So each sealed root is hash-chained to the one before it and stamped into a Bitcoin block through OpenTimestamps. Re-check any of them live against a public block explorer, or take the portable proof and verify it with nothing of ours involved.

No anchors sealed yet — the first is created on the next tick.

03The log itself

What is going into it, right now

Entries are listed by a hashof their id, never the id. That is on purpose: a proof can be pulled for any id you already hold, so publishing them here would let anyone walk this log and enumerate other companies' runs and agents. You can verify what you hold; you cannot browse what you do not — which is why the example above exists.

No entries yet.

Everything here is a public API, with no key
GET /transparency/head · /transparency/log · /transparency/proof/{id}
GET /transparency/anchors · /transparency/anchor/{id}/proof · /verify
Verify from your own terminal