# AgentKV – Encrypted Key-Value Read (GET)

> AgentKV – Encrypted Key-Value Read (GET) is a paid API for AI agents from api.agentx402.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Reads a value from an agent-native, client-side encrypted key-value store using a wallet-scoped namespace, billed per request via x402 micropayment.

## Facts

- Endpoint: GET https://api.agentx402.ai/v1/kv/final-1785132418
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentkv-encrypted-key-value-read-get-9c84cbb3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hsBUurNK8Yy4r2kA4Dvyl

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 agentkv-encrypted-key-value-read-get-9c84cbb3
```

Example prompt: Read the value stored under the key 'final-1785132418' in my AgentKV store — use my wallet as the namespace and charge the $0.003 read fee.

## When to prefer this

Choose this endpoint when your AI agent needs to retrieve previously stored state, secrets, or configuration without any signup or API key — especially when operating in a wallet-native or x402-payment environment. It is ideal for stateless agents that need persistent memory between sessions, or for sharing encrypted data across agent instances scoped to the same wallet. Prefer it over traditional KV stores when the agent already handles x402 micropayments and requires client-side encryption by default.

## Known failure modes

- Key not found (404) — the specified key does not exist in the wallet-scoped namespace
- Insufficient credits or payment failure — x402 payment rejected, no credits or wallet balance
- Unauthorized namespace — wrong wallet or ak_ key used to access a key owned by a different namespace
- Malformed request — invalid key path format or unsupported HTTP method
- Service unavailable — API temporarily down (5xx)

## How this service works

Agent-native encrypted key-value store, paid per request over x402 — no signup, no API key. The payer's wallet (or an ak_ account key) is the namespace; values are client-side encrypted. Write $0.005, read $0.003; prepay $1 = 10,000 credits at 1/10 the per-op price (POST /v1/credits/deposit). SDK: npm i @agentkv/client. Docs: https://agentx402.ai

## Output

Returns the stored value associated with the key path in the URL (e.g. /v1/kv/final-1785132418). The value was previously written by the agent and is client-side encrypted, so the response contains the encrypted payload which the client decrypts locally. On success, a 200 response with the value is returned; the $0.003 USDC read fee is charged via x402 micropayment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentkv-encrypted-key-value-read-get-9c84cbb3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentx402.ai](https://www.zero.xyz/host/api.agentx402.ai/llms.txt)