# Pyfile x402 API – Encrypted Secret Storage (PUT)

> Pyfile x402 API – Encrypted Secret Storage (PUT) is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-12).

Stores an encrypted secret value server-side using AES-256-GCM and returns a one-time-read dead-drop ID and access token for later retrieval

## Facts

- Endpoint: POST https://pyfile-agent.taile3ff35.ts.net/secret/put?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pyfile-x402-api-encrypted-secret-storage-put-b5454657
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e9CDkqipd2H17usiac5KM

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 pyfile-x402-api-encrypted-secret-storage-put-b5454657 -d '<json body>'
```

Example prompt: Securely store this API key 'sk-abc123xyz' as an encrypted dead drop so I can share the retrieval token with someone else who can only read it once.

## When to prefer this

Choose this endpoint when you need to pass a sensitive value (API key, password, token) between agents or humans in a one-time-read, zero-persistence manner. It is preferable to plaintext sharing, environment variable hacks, or persistent secret stores when you want the secret to self-destruct after one retrieval. It is pay-per-call at $0.002 USDC, making it cost-effective for individual agent workflows that need ephemeral encrypted storage without managing a full secrets vault.

## Known failure modes

- Missing or malformed request body returns an error
- Payment not provided or insufficient USDC/XNO balance causes a 402 Payment Required response
- Server-side encryption failure may return a 500 error
- Attempting to store an excessively large payload may be rejected
- Network timeout to the Tailscale-hosted endpoint may result in connection errors

## How this service works

Store a secret (credential, token, key) for later retrieval — encrypted at rest (AES-256-GCM). Returns an id + access token; fetch later by id+token. Max 16KB. For agent state that must survive across runs.

## Output

Returns a JSON object containing a unique secret ID (e.g. sec_abc123), a one-time access token (e.g. tok_9f2c...), an ok:true confirmation, and a note confirming the value is encrypted at rest with AES-256-GCM. The secret can only be retrieved once using the returned ID and token.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "sec_abc123",
  "ok": true,
  "note": "Store id+token; value encrypted at rest (AES-256-GCM).",
  "access_token": "tok_9f2c..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pyfile-x402-api-encrypted-secret-storage-put-b5454657/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net/llms.txt)