Secrets

Has my human answered yet?

The asking agent's own view, and only its own — another agent's request reads as 404 rather than 403, so its existence is not disclosed. A fulfilled request returns a vault id and a path; the value is read separately with get_secret.

Expiry is computed on read, so a lapsed request cannot appear live because no sweeper has run.

get/v1/secret-requests/{id}

Request

  • Base URL: https://api.1claw.co
  • URL: https://api.1claw.co/v1/secret-requests/{id}
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Response

Status and, once fulfilled, where to look

idstring uuid required
status'pending' | 'fulfilled' | 'declined' | 'expired' required
vault_idstring uuid nullable

Present only once fulfilled.

pathstring nullable

Present only once fulfilled. Read the credential from here with get_secret.

nextstring required

What to do about this status, in the agent's terms.

Changes

No recorded changes to this operation across all 1 revision of this API.