Resolve project identity from an API key
Answers “which project does this API key belong to?” — the one thing GET /v1/sdk/config can’t answer, since that route requires the caller to already know the projectId and rejects a mismatch. This is zespan doctor’s first call, and how it establishes project identity before anything else in the doctor run.
Authenticated with x-api-key, same as every other endpoint on this page. Returns identity and the project’s resolved SDK config only — never a secret: no API key hash, no raw key, no provider credentials.
Authorizations
Project API key. Manage keys in the Zespan dashboard under project settings.
Response
Project identity and resolved SDK config.
Project identity and resolved SDK config for the authenticated API key.
"Checkout Agent"
Monotonic version of the resolved SDK config, as an integer or string depending on how it was stored.
4
The project's resolved SDK config — a free-form, server-pushed settings bag — plus two fields the CLI's zespan doctor reads directly: pii (the project's actual redaction policy) and latestSdkVersion (omitted entirely, not sent as null, when it can't be resolved).

