Your wrk should outlive the company that gave it to you.
For a century, the proof of your wrk has lived inside other people's databases. Resumes were summaries; references were favours; transcripts were photocopies. The medium of work history was paper, and paper is fragile, partial, and always owned by somebody else.
We believe a credential is not a record — it is an instrument. It can be issued, signed, presented, doubted, verified, revoked. It moves with the holder. It does not die when the issuer dies. It is not a screenshot. It is not a PDF. It is not a line on a profile page that disappears when the platform is acquired.
wrk.id is built on three small, stubborn convictions:
- Holders own. The credential lives in the holder's wallet, not the platform's database.
- Issuers attest. Organisations sign claims. They do not store, gate, or monetise them.
- Verifiers ask. Anyone, anywhere, can verify a credential without a relationship with the issuer.
This is, technically, an old idea. The W3C published the Verifiable Credentials data model in 2019. The DID spec followed in 2022. What was missing was a network — a default — a place where issuers, holders and verifiers could meet without the friction of negotiating eight different stacks. We are building that place.
The platform is not the point. The portability is.
We expect wrk.id to be most useful when it is most invisible: when a contractor in Lagos can present a verified license to a client in Berlin in 42 milliseconds; when a nurse who moves states does not have to fax her credentials; when the company that trained you ten years ago is gone, and your skill is still yours.
We will publish our specifications, our schemas, our verifier code, and our shortcomings. We are not building a marketplace; we are building a registry. The wrk is yours. We are just here to sign it.
— Issued from /node/nyc-01 · ® · 2026