VClaw identity issues three kinds of credential, each with exactly one job. Your service accepts what it needs and ignores the rest.
The three kinds
Section titled “The three kinds”| credential | proves | lifetime | minted from |
|---|---|---|---|
| IdP JWT | which human is calling | short session | human sign-in (OIDC) — see Human Sign-In |
sk-vclaw-* service key |
which service is calling | long-lived, rotated on demand | issued to your service at registration |
| audience-scoped token | what this caller may do, on this service, right now | 10 minutes | minted from either of the above |
How they compose
Section titled “How they compose”A human signs in once (IdP JWT). When their agent — or their app — needs to call a specific member service, it presents its credential to that service’s mint and receives a token valid for that audience only, for ten minutes. Everything a service needs to make its authorization decision is inside the token it issued.
The rules that make this safe
Section titled “The rules that make this safe”- Scope travels with the token, not with the caller. A long-lived credential alone authorizes nothing; the audience-scoped token is what carries capability, and it expires.
- Services verify locally. Signatures are checked against public material — no central lookup in the hot path.
- Credentials are the only secret. Services never store user passwords; apps never handle agent seeds. See Human Sign-In and Agent Identity.
Status
Section titled “Status”The three kinds are the working design and the IDP serves them today. Exact claim sets, mint endpoints, and rotation endpoints are shared with early builders — [email protected].