# Agentic Endpoints Testnet Vault Store

> Agentic Endpoints Testnet Vault Store is a paid API for AI agents from agentic-endpoints-testnet.oliver-835.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Store a client-side encrypted item in an isolated vault namespace, claiming the namespace on first store and returning a one-time namespace_token.

## Facts

- Endpoint: GET https://agentic-endpoints-testnet.oliver-835.workers.dev/vault/store
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentic-endpoints-testnet-vault-store-fe11bcc1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qQZjTmn-ZjqLAXr-GCKef

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 agentic-endpoints-testnet-vault-store-fe11bcc1
```

Example prompt: Store my AES-256-GCM encrypted payload under the key 'api-key-prod' in the namespace 'my-agent-secrets' — this is the first item so it should claim the namespace and give me back the namespace token.

## When to prefer this

Use this endpoint when you need to persist client-side encrypted data in an isolated namespace that only token-holders can access, especially when you want zero server-side plaintext exposure. Prefer this over generic key-value stores when you need namespace isolation with a one-time token claim pattern and support for TTL-based expiry.

## Known failure modes

- Missing namespace_token on a previously claimed namespace returns an authorization error
- Invalid or expired namespace_token returns a 401/403 error
- Missing required fields (namespace, key, ciphertext) returns a 400 validation error
- Duplicate key in same namespace may overwrite or conflict depending on service behavior
- Expired TTL on a previously stored item may cause retrieval failures later
- Payment not provided or insufficient USDC balance returns a 402 Payment Required

## How this service works

Store an encrypted item in the vault. The first store claims the namespace and returns a one-time namespace_token.

## Output

Returns a confirmation that the encrypted item was stored, and on the first store in a new namespace, returns a one-time namespace_token that must be used for all subsequent reads, writes, deletes, and checks in that namespace.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "alg": {
   "type": "string",
   "description": "Encryption algorithm label (default aes-256-gcm)"
  },
  "key": {
   "type": "string",
   "description": "Item key"
  },
  "ttl": {
   "type": "number",
   "description": "Optional lifetime in seconds"
  },
  "namespace": {
   "type": "string",
   "description": "Vault isolation scope"
  },
  "ciphertext": {
   "type": "string",
   "description": "Client-side encrypted payload. This service never sees plaintext."
  },
  "namespace_token": {
   "type": "string",
   "description": "Required once the namespace has been claimed by a first store"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentic-endpoints-testnet-vault-store-fe11bcc1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentic-endpoints-testnet.oliver-835.workers.dev](https://www.zero.xyz/host/agentic-endpoints-testnet.oliver-835.workers.dev/llms.txt)