# ncrypted.ai One-Time Secret Storage

> ncrypted.ai One-Time Secret Storage is a paid API for AI agents from ncrypted.ai, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-17).

Stores a client-side encrypted secret (password, API key, or note) server-side and returns an ID for building a self-destructing share link

## Facts

- Endpoint: POST https://ncrypted.ai/api/v1/secrets?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ncrypted-ai-one-time-secret-storage-3a276e00
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hVLa-zS-VQxi7pftdJxHO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ncrypted-ai-one-time-secret-storage-3a276e00 -d '<json body>'
```

Example prompt: Store this API key as a one-time encrypted secret that self-destructs after the first read and expires in 24 hours: 'sk-abc123xyz789'

## When to prefer this

Choose this endpoint when you need to share a sensitive value (password, API key, token, note) exactly once with guaranteed destruction after reading, or when secrets must not persist beyond a defined TTL. Ideal for agent-to-agent credential handoffs, onboarding flows, or any scenario where a secret must be transmitted without leaving a persistent copy. Prefer over general-purpose secret managers when zero-persistence and self-destruction are the primary requirements.

## Known failure modes

- Invalid or malformed encrypted payload — secret not stored, 400 error returned
- TTL value out of acceptable range — request rejected with validation error
- Secret already consumed (read once) — subsequent access attempts return 404
- Secret expired past TTL — returns 404 or expiry error
- Payment failure via x402 protocol — request blocked before processing
- Server-side storage error — 500 returned, no ID generated

## How this service works

ncrypted: store a client-side encrypted, one-time secret (password, API key, note). Returns an id; the client builds the share link /s/{id}#{key}. The secret self-destructs after one read or at ttl. Use the `ncrypted` npm SDK or @seidl-family/ncrypted-mcp to encrypt.

## Output

Returns a secret ID (e.g. a UUID or short token) that the client uses to construct a shareable link in the format /s/{id}#{key}, where the fragment (#key) is the client-side decryption key that never touches the server. The secret payload is destroyed server-side after a single read or when the TTL expires.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ncrypted-ai-one-time-secret-storage-3a276e00/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ncrypted.ai](https://www.zero.xyz/host/ncrypted.ai/llms.txt)