# AgentKV Read (GET)

> AgentKV 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 at a specific key, paid per-request via x402 micropayment

## Facts

- Endpoint: GET https://api.agentx402.ai/v1/kv/canary-kv-1785214918
- 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-read-get-a363a483
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uQVuq4U5LRZpsmIVxHL95

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-read-get-a363a483
```

Example prompt: Read the value stored under key 'canary-kv-1785214918' from my AgentKV store — use my wallet as the namespace and pay the read fee automatically.

## When to prefer this

Choose this endpoint when an AI agent needs to read back a value it (or another authorized agent) previously stored, without any signup or API key — just a wallet or ak_ key and a $0.003 USDC micropayment. Ideal for agent memory, shared secrets, runtime configuration, or cross-agent state passing where privacy (client-side encryption) and permissionless access are required. Prefer this over traditional KV stores or secret managers when operating in a serverless, wallet-native, or x402-compatible agent environment.

## Known failure modes

- 402 Payment Required — x402 micropayment header missing or insufficient; agent must attach $0.003 USDC payment
- 404 Not Found — key does not exist in the namespace or namespace mismatch (wrong wallet)
- 401 Unauthorized — ak_ account key invalid or expired
- Decryption failure — client-side: key was written by a different keypair
- Rate limiting or credit exhaustion if using prepaid credit account

## 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 requested key within the caller's wallet-namespaced AgentKV store. The value was encrypted client-side at write time, so the agent must decrypt it locally. Response includes the encrypted blob or decrypted value depending on SDK/client handling. Returns a 402 Payment Required if payment was not attached, or a 404/empty if the key does not exist.

## 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-read-get-a363a483/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)