You've proven your age to eleven websites. They all kept your ID.
Trustable is a reusable verification credential. Verify your identity once, let websites verify your identity with the information you want to give.
In practice
A rental marketplace asks whether you're over 18. You approve. It receives age_over_18: true, signed and time-boxed.
Your birth date, your name, your document — none of it leaves Trustable.
- 14:02:11Acme RentalsRequested proof — verified_person, age_over_18 — “Age-restricted marketplace access”
- 14:02:48Jordan L.Approved 2 of 2 claims — Consent recorded. Birth date, name, and documents withheld.
- 14:02:49TrustableIssued signed token — ES256 · sub: pairwise pseudonym · expires 14:07:49
- 14:02:50Acme RentalsVerified token — { "verified_person": true, "age_over_18": true } — nothing else received
01 — Process
Three steps, once
The verification happens a single time. Everything after is a question and an answer.
Verify your identity once
A single verification session — document, liveness check, done. The result is a credential that lives in your Trustable account, not in a company’s database.
A business asks a question
When a marketplace or platform needs to know something — are you over 18, are you a real person — it sends a request naming exactly which facts it wants and why.
You answer, or you don’t
The consent screen lists each requested fact next to what will not be shared. Approve, and Trustable signs a token containing only the answers. Deny, and nothing moves.
02 — For businesses
Trust without custody
Most platforms don't want identity documents — they want the answers those documents contain. Trustable hands over the answers and keeps the documents out of your infrastructure entirely.
- Fewer fake accounts
- Each credential maps to one verified person, and each app receives a stable pairwise pseudonym. Duplicate sign-ups become visible without any identity data changing hands.
- Less data to hold
- You receive signed booleans — age_over_18: true — not birth dates, not document scans. There is nothing sensitive in your database to breach.
- Faster onboarding
- A user who verified last month proves facts to you in one consent screen. No re-upload, no review queue on your side.
- One small API
- Create a request, redirect the user, verify the returned token. Three endpoints, plain JSON, keys you can revoke.
03 — Selective disclosure
The birth date stays home
A liquor delivery service needs one bit of information: over 18, yes or no. It does not need the day you were born, and once it has that date it can never un-know it. Trustable reduces every identity question to the smallest answer that satisfies it.
Prove the fact. Keep the data.
exchange — acme-rentals × jordan
Asked
Is this user over 18?
Answered
{ "age_over_18": true }
Withheld
Birth date, legal name, document images, address — everything else.
Signed ES256 · expires in 5 minutes · valid for this application only
04 — Integration
An afternoon, not a quarter
Create an authorization request, send the user to the consent URL, verify the token they come back with. The response below is real — it's what the demo API returns today.
POST /api/v1/verification-requests
{
"application_id": "app_acme123",
"claims": ["verified_person", "age_over_18"],
"purpose": "Age-restricted marketplace access"
}
// 201 Created
{
"id": "req_8f21ab",
"status": "pending",
"authorization_url": "/authorize/req_8f21ab",
"expires_in": 3600
}Verify once. Answer forever.
Create a credential in about two minutes, or wire claim verification into your product before lunch. Both paths start here.