# ZenVault Key-Value Vault (POST /v1/vaults)

> ZenVault Key-Value Vault (POST /v1/vaults) is a paid API for AI agents from api.zenvault.eu, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Creates a new key-value storage vault with TTL that persists data across agent runs, returning the created resource and a one-time management token.

## Facts

- Endpoint: POST https://api.zenvault.eu/v1/vaults?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zenvault-key-value-vault-post-v1-vaults-f85e4cd6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eQBWbd_0HT6F1X9Zu7X07

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 zenvault-key-value-vault-post-v1-vaults-f85e4cd6 -d '<json body>'
```

Example prompt: Create a new ZenVault key-value vault to store my workflow state — it should expire after 24 hours and hold the current progress of my data pipeline job.

## When to prefer this

Choose this endpoint when your agent needs durable, cross-run state storage with automatic expiry — ideal for workflows that may crash and resume, multi-session data sharing, or temporary config/state that should self-clean via TTL. Prefer this over in-memory state when runs are non-contiguous, and over full databases when you need lightweight, ephemeral, managed storage without provisioning overhead.

## Known failure modes

- Invalid or missing TTL value returns a 400 error
- Payment not included or insufficient USDC balance returns a 402 Payment Required
- Malformed request body returns a 422 Unprocessable Entity
- Vault quota exceeded for the account returns a 429 or 403
- Service unavailability returns a 503

## How this service works

Key-value storage with TTL that survives your runs.

## Output

Returns a JSON object containing the newly created vault resource (including vault ID, key-value contents, and expiry/TTL metadata) along with a one-time management token used to update or delete the vault later.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zenvault-key-value-vault-post-v1-vaults-f85e4cd6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zenvault.eu](https://www.zero.xyz/host/api.zenvault.eu/llms.txt)