Verify a Credential
Verify a presented credential and return a structured outcome.
The verifier runs a deterministic pipeline against the JWT-VC: parse, resolve
the issuer’s signing key from the published JWKS, check the ES256 signature,
validate the standard claims (iat / exp / nbf, and audience if
provided), confirm the payload matches the credential-type schema, look up
the live revocation status, and — for agent credentials — evaluate the
authorization policy against the supplied request context.
Verification outcomes (revoked, expired, signature mismatch, policy denied,
etc.) return HTTP 200 with { valid: false, reason } so callers can branch
on outcome without try/catching transport errors. Only infrastructure
failures use the error envelope.
Documentation Index
Fetch the complete documentation index at: https://docs.beltic.com/llms.txt
Use this file to discover all available pages before exploring further.
Body
Response
Verification result — valid: true on success, valid: false with reason on domain-level failure
- Option 1
- Option 2
true business, user, agent_authorization, outcome_attestation - Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
active, revoked, expired, suspended self_attested, liveness_verified, idv_verified, enterprise_verified 501 - 512