Secrets

Ask a human for a credential

Agent-authenticated. The agent says what it needs and why; the human sees a secure field in the dashboard, stores the value straight into the vault over their own session, and the agent is later told where it went — never what it is.

This exists because the alternative is worse than it looks. Typing a credential into runtime chat persists it to the conversation, writes it into the agent's memory, and replays it to the model on every later turn: one paste, four copies, no way back.

One open request per agent per label: asking again with the same label refreshes the existing one rather than queueing a duplicate. Unanswered requests expire after 24 hours.

post/v1/secret-requests

Request

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

Request body

labelstring required
purposestring required

Shown to the person being asked. They are handing over a secret and need to know what for.

suggested_pathstring nullable

A suggestion only — the human picks the vault and may change the path.

Example request

{
  "label": "X API access token",
  "purpose": "To post the daily update to X on your behalf.",
  "suggested_path": "api-keys/x-access-token"
}

Response

Asked. Poll the status route; do not ask in conversation.

idstring uuid required
statusstring required
expires_atstring date-time required
nextstring required

Example response

{
  "status": "pending"
}

Changes

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