putty
API ReferenceLedger

Which projects a secret is usable from

Reports the projects a secret is usable from. A user-scoped secret is usable from every one of the caller's projects; a project-scoped secret is usable from exactly its own. Metadata only.

GET
/secrets/usage/{name}

Reports the projects a secret is usable from. A user-scoped secret is usable from every one of the caller's projects; a project-scoped secret is usable from exactly its own. Metadata only.

Authorization

bearerAuth
AuthorizationBearer <token>

A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.

In: header

Path Parameters

name*string

The environment-variable-shaped name of the secret. PRIVATE_KEY, MNEMONIC, and SEED_PHRASE are refused.

Match^[A-Z][A-Z0-9_]{0,63}$

Query Parameters

projectId?string

Read the project-scoped secret of this name.

Length1 <= length

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/secrets/usage/string"
{  "name": "string",  "scope": "user",  "usableInProjects": [    {      "projectId": "string",      "projectName": "string"    }  ]}

Which secret a name resolves to in a project GET

Reports which scope a name resolves to inside a project: `project` when a project secret shadows a user one, `user` when only the user-scoped secret exists, `none` when neither does. The `shadowed` flag says whether a user-scoped secret of the same name is present behind a project-scoped winner. Metadata only.

List the caller's pending secret requests GET

Returns the requests the model has made for a value, newest first. Each one is a prompt the dashboard renders as a secure input: the user types the value there, never in chat. The model is told only whether a request is `pending`, `set`, or `declined`; it never learns the value.