Back to Browse
Agentic Endpoints Testnet Vault Store
x402
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.
Price / call$0.02
Success—
StatusUnknown
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.
Example use cases
Initialize agent secrets vault
“I need to create a new encrypted vault for my agent's secrets. Store this AES-256-GCM ciphertext under the key 'openai-key' in the namespace 'agent-config' — it's the first item, so claim the namespace and return the namespace token.”
Persist encrypted credential with TTL
“Store my encrypted API credential ciphertext under the key 'stripe-secret' in the 'payment-agent' namespace with a 3600-second TTL. I already have the namespace token from when I first claimed it.”
Save encrypted session state
“Save this encrypted session state blob under the key 'session-2024' in my 'workflow-agent' vault namespace. The namespace is already claimed — here's my namespace token. Use AES-256-GCM.”
Technical details
Endpoint
GEThttps://agentic-endpoints-testnet.oliver-835.workers.dev/vault/storeWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| alg | string | Encryption algorithm label (default aes-256-gcm) |
| key | string | Item key |
| ttl | number | Optional lifetime in seconds |
| namespace | string | Vault isolation scope |
| ciphertext | string | Client-side encrypted payload. This service never sees plaintext. |
| namespace_token | string | Required once the namespace has been claimed by a first store |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"