ckrets.aickrets.ai Beta
Menu
Get a free keyFree key
Docs menu

ckrets docs

ckrets hands a secret to one named recipient (a person, an agent, a CI job or a server) through a one-time token. Start with the guide; every page here is also served as Markdown for agents.

Start here

  1. Make a first secret with one curl call and no key: create and reveal, complete.
  2. Keep the value out of your servers and transcripts: reveal it straight into the process that uses it (the helper).
  3. Name the recipient (a key, a CI job's OIDC identity or a public key) so a leaked link is worthless: audiences.
  4. Handle limits and errors by their type: limits and errors.

Pages

Quick startThe one safe path: create for a named recipient, then reveal into the program that uses it. Guide: create and revealEvery flow, complete: create, reveal into a process, keys, audiences, CI, the MCP server. Start: examples by use caseOne runnable example for every use case, then the API, keys, limits and errors on one page. ErrorsEvery problem type the API answers, its status and what to do next; each has its own page at /problems/<type>. LimitsThe tier table, the headers, every error type and what to do next, what we keep and for how long. ReceiptsThe signed receipt every create and reveal returns, and how to check it offline. Signing requestsRFC 9421 signatures: prove you are a publicKey recipient; make the keys. Client-side encryptionNo-view secrets: the formats for ciphertext and wrapped keys. Agent skill (SKILL.md)The same guidance packaged as an agent skill. CI hand-offsA CI job hands a fresh credential to a server or a later job, with no ckrets key stored. Endpoints and credentialsEvery endpoint by stage, and what each kind of bearer can do. The puzzle templateRiddle, game and dated boxes, as the Puzzlebox app uses them. Beta termsThe terms for using ckrets during the beta. PrivacyWhat we collect, why, how long we keep it, and who else handles it. Can ckrets read my secrets?Which modes we can read and which we cannot, how to check it yourself, and the objections answered.

For agents and tools

The same content, machine-readable. Fetch /llms.txt first.

/llms.txtThe index for agents, with the rules that matter. /llms-full.txtEvery doc as one file. /openapi.jsonOpenAPI 3.1 with an example for every call (/openapi.yaml is the source). /mcp-tools.jsonThe MCP server's tools; the server is https://ckrets.ai/mcp. /.well-known/ckrets.jsonCapabilities, tiers, endpoints, retention. /problems/<type>One page per error type: what it means, what to do next. Every type is listed on the error types page.