# Pyfile x402 API – Encrypted Secret Drop with TTL

> Pyfile x402 API – Encrypted Secret Drop with TTL 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-11-16).

Stores an encrypted secret as a one-time-readable dead drop with a time-to-live expiry, returning a read URL that auto-destructs after the TTL or first read.

## Facts

- Endpoint: POST https://pyfile-agent.taile3ff35.ts.net/secret/drop-ttl?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pyfile-x402-api-encrypted-secret-drop-with-ttl-6f2a2042
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qajpV6mX4iUPQPaFdpjMb

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-drop-with-ttl-6f2a2042 -d '<json body>'
```

Example prompt: Create a one-time dead drop for this API key 'sk-abc123xyz' that expires in 24 hours and give me the read URL to share with my colleague.

## When to prefer this

Choose this endpoint when you need a guaranteed one-read-then-destroy pattern for sensitive data with a hard expiry deadline, especially in agent-to-agent workflows where secrets must not persist. Prefer it over generic secret managers when you want automatic TTL-based destruction without manual deletion and when paying per-use via x402 (USDC on Base or XNO) is acceptable.

## Known failure modes

- Missing or malformed secret payload returns a 4xx validation error
- Payment failure via x402 protocol results in 402 Payment Required with payment details
- TTL value out of acceptable range may return a 400 Bad Request
- Secret already read or expired returns 404 on the read URL
- Network timeout on the Tailscale-hosted endpoint if node is offline

## How this service works

Pay-per-call endpoints for AI agents: web search, web-to-markdown reader, LLM chat completions, encrypted secret storage with one-read dead drops, and a business-idea generator. Payment over x402: USDC on Base, or XNO on nano:mainnet.

## Output

Returns a JSON object containing a unique drop ID, an ok confirmation, a human-readable note explaining the read-once-then-destroy behaviour, a relative read URL path, and an ISO 8601 expiry timestamp after which the secret is permanently destroyed.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "drop_ttl_xyz",
  "ok": true,
  "note": "Readable until TTL expires, then destroyed.",
  "read_url": "/secret/drop-ttl/drop_ttl_xyz",
  "expires_at": "2026-09-23T14:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pyfile-x402-api-encrypted-secret-drop-with-ttl-6f2a2042/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)
