One record, owned by the person who earned it, and the tools for building it, holding it, handing it over and checking one you were handed. This page lists every product name we use, what each one does today, and which ones are still just names.
What the record is made of, what you hold, and how work you already did gets into it.
Work history, education, skills and certifications, in one record you own.
Every entry states its provenance next to the entry. Something a counterparty confirmed reads as confirmed. Something you typed reads as self-reported, and no amount of time or payment converts one into the other.
What you already hold, and a version of it you can hand to somebody.
Credentials in their real state, expired and declined included, plus an export in JSON Resume and JSON-LD and a printable sheet that needs no share link. Credentials are issued as W3C Verifiable Credentials signed with Ed25519 by a did:web issuer, and anyone can check one offline against the published keys. Disclosure is three scopes: full, band, or band only.
Your credentials and career export (the page is called Credentials and career export)
Bring in work from a platform you already used.
Upload the export a platform gave you and the jobs in it land on your record marked self-reported, with the client who could confirm each one. It creates no scoring event by itself. Importing five years of work does not move a score, and it is not supposed to.
Connect a tool you already use, and let it bring evidence in for you.
Authorize a system you already work in and Credda reads what it says about work you did, so the record fills without you retyping it. Every connection is read-only, the page states exactly what each one reads before you authorize it, and ending it here revokes the access at the provider rather than only forgetting the token. Stronger evidence than an upload for one reason: a file is something you could have edited, and an authorized system is not.
Desktop and mobile, and an honest note about which builds exist today.
The whole product works in a browser today, phone included. The apps page says which builds ship, which are still being written, and what to use in the meantime. It never offers a download that is not there, which is the only reason this row can sit in a product list at all.
Somebody chose to send you their record. These are the tools for reading it and proving it is real.
Check a record or a signed credential, without an account.
Paste a share link or a username and read the record the subject published. Or paste a credential and verify the signature in your own browser against Credda public keys, which is the part that does not require trusting a live Credda response. A share token is the consent: revoke it and everything made from it stops resolving.
Look up a record you were given (the page is called Find a Credda user)
For work an organization ran, and for software that needs the same record.
Record the work your team did. The people who did it keep the record.
Rosters, completed work and shifts a manager witnessed. Confirming is free on every plan. The Work Score an organization sees is scoped to that organization and is never an input to the portable score, so a manager cannot move somebody’s public number by rating them.
One documented REST API behind everything above.
Score reads, event reporting with idempotency keys, disputes and usage metering, all under a published OpenAPI 3.1 contract. Webhooks are HMAC-signed with replay protection and a per-attempt delivery log you can replay. Published packages today: a TypeScript SDK, a command line client, and an MCP server. The developer platform organizes the whole surface into six areas, which are parts of this one product rather than products of their own.
API and SDKs (the page is called Credda for developers)
The six API areas, endpoint by endpoint (on the developer platform)
Software acting on its own behalf, as a first-class subject.
An agent is a subject, not only a client of the API. It can be registered through /api/v1/agents, and the outcomes it delivers are recorded as delivery receipts: only deliveries a distinct counterparty confirmed count as evidence, and an operator vouching for its own agent is recorded but never counted. Anyone holding a share token can view that record at /a/:token, the non-human sibling of the person and company record pages, and download the signed credential. The MCP server is still how an agent reads a counterparty or presents its own record mid-task.
Register an agent and issue receipts (the page is called Credda for developers)
The issuer directory: who may issue what, and how to check it.
The parts that make a registry useful were already live: the issuer is did:web, the signing keys are published and fetchable, revocation runs on StatusList2021, and every credential response carries its issuer document and registry location. Now there is a page that renders them: a browsable directory built from the well-known documents the host publishes, listing each issuer, the credential types it may issue, its published keys and the one revocation list.
Track the businesses you pay: their documents, what is current or expired, and that they are real.
Collect the insurance certificates, tax forms and registration a vendor hands you, and see at a glance what is current and what has lapsed. It is your own record of the companies you pay, never a report about a person, and it decides nothing for you. The existence check confirms a real registered business on the same staff-audited basis as the company badge, and a plan buys the workflow and faster review, never the outcome.
What gets recorded in your trade, and who confirms it. A page for each.
Twenty-eight trades, from home care to freight to dental. Each page lists the outcomes a record is built from in that work, names who confirms each one, and says what never goes on the record of the person who did the job. A shift the site cancelled is not that person’s outcome, so it never lands on them.
A name was drafted for the fraud and collusion work. It is being retired rather than built, and the reason is worth stating plainly.
The machinery is real. Credda runs deterministic checks for collusion, duplicate accounts and unusual velocity across the whole graph of confirmations. They exist so that a ring of accounts confirming each other does not turn into evidence.
Those checks are advisory. They never change anybody’s score, they are reviewed by Credda staff, and they are not for sale. Packaging them as a product would mean selling conclusions about a person to whoever pays, which is a different company from this one. Credda renders no verdict and does not rank people. It records what somebody else confirmed, and it shows its working.
No plan and no payment moves a score, on any product, at any price. What you pay for is convenience: seats, volume, retention. Asking somebody to confirm your work is free on every plan and always will be, because charging for it would make the evidence a function of the budget.
The score itself runs on a published formula, version 5.6, with five weights and six bands from Distinguished down to At Risk. You can read the whole model, or watch the loop run end to end with a worked example. What Credda refuses to do is written down on the same page as the formula, deliberately.
