Introspect the credential
Returns the authenticated credential: the workspace it is bound to, how it authenticates, and its effective scopes. Use this to preflight whether the key can perform writes (write) or admin actions (admin) before calling a mutating endpoint. Keys minted before scoping existed report ["read"] — the access the scope gate actually grants them.
Authorizations
Clerk API key. Create one in Settings → API Keys. Pass as Authorization: Bearer <key>.
Response
200 response
The authenticated credential: workspace binding, kind, and effective scopes.
The workspace this credential is bound to.
"org_2abc..."
How the request authenticated: api_key (REST v2 key — the only kind the public API serves today), session (UI cookie), or direct (the internal CLI's in-process transport).
api_key, session, direct "api_key"
Clerk API key id (ak_...) when authenticated with a key, else null.
"ak_2abc..."
Effective scopes of the credential. Keys minted before scoping existed carry no explicit scopes and are enforced as read-only, so they report ["read"] here — exactly what the scope gate applies.
One API scope. read < write < admin (each implies the previous).
read, write, admin User the request acts as (an API key acts as the user who minted it), when known.
