Read verified data

🔑 Auth: the user’s Bearer valyd_access_token · 💸 Free — reads never cost a check · 🔒 Proofs and public data only, never PII

Three reads cover everything the account already holds:

API	One call gets you
`GET /oidc/userinfo`	Who they are — legal name, username, country, `id_verified`
`GET /oidc/licenses`	Professional licenses already verified on their account
`GET /oidc/verifications`	Every proof and badge — KYC done, age bands, license badges


const proofs = await valyd.auth.getVerifications(accessToken);
if (proofs.id_verified) {
  // KYC already done — you're finished. No check, no cost, no PII stored.
}

This is the KYC-reuse story: the user verified once — maybe in another app. You check the status, you don’t re-run it, and you never store personal data.

Raw identity attributes (DOB, document fields) are separate — the user approves them explicitly via the consent flow.

Reads are only half of it — with the same token you can re-prove who they are, right now: match their face before a sensitive action, confirm their location, or re-check a live license. See what the verification APIs let you build.

Something missing? Run a configured workflow on a Reusable Verification session with the user’s token — face match, liveness, license, age, location, and KYC are all available as workflow checks (see the checks reference). The user completes them on Valyd’s verification page, and the passed proofs save back to their Valyd ID.