Read the caller's profile
Returns the per-caller profile: the visitor's display name and the chosen Putty brand avatar. Both fields are nullable; a fresh visitor has not set them yet, and the Settings page renders an empty form in that case.
Returns the per-caller profile: the visitor's display name and the chosen Putty brand avatar. Both fields are nullable; a fresh visitor has not set them yet, and the Settings page renders an empty form in that case.
Authorization
bearerAuth 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
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/account/me"{ "id": "string", "displayName": "string", "avatarId": 1}Revoke an API key DELETE
Soft-deletes the key: the row stays so the audit trail is intact, but the SHA-256 hash is dropped from the verify index, so every future MCP request that presents the key receives 401. The endpoint returns 404 when the key does not exist or is owned by a different user; it does not differentiate, so it cannot be used to probe other users' key ids.
Update the caller's profile PATCH
Updates the per-caller profile. Both fields are optional; a caller can update one without touching the other. `displayName` is trimmed and capped to 80 characters; an empty string is treated as `null` and clears the saved value. `avatarId` is the 1-based index of the chosen Putty brand avatar (`avatar-1.png` … `avatar-20.png`); values outside the range are rejected with a 400.