# AgentKV — Read Key (GET)

> AgentKV — Read Key (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-15).

Reads and returns the client-side encrypted value stored under a specific key in the caller's wallet-namespaced key-value store, paid per request via x402.

## Facts

- Endpoint: GET https://api.agentx402.ai/v1/kv/canary-kv-1785245249
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentkv-read-key-get-f58982f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MWrXlqVO4GyGQKNMmB66t

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-key-get-f58982f6
```

Example prompt: Read the value stored under the key 'canary-kv-1785245249' in my AgentKV store and return whatever's there — pay the $0.003 read fee from my wallet.

## When to prefer this

Use this endpoint when an AI agent needs to retrieve a previously stored, encrypted value from a persistent key-value store without requiring any signup or API key — authentication is handled entirely via the caller's crypto wallet or ak_ account key. Prefer AgentKV over generic KV APIs when you need agent-native x402 micropayment billing, client-side encryption by default, and wallet-scoped namespacing. Choose the GET (read) operation when you need to look up state, cached data, credentials, or configuration that was written in a prior session.

## Known failure modes

- Key not found — returns 404 if the key has never been written or was deleted
- Payment failure — x402 payment header missing, insufficient funds, or rejected wallet returns 402
- Namespace mismatch — reading a key that belongs to a different wallet/account returns 403
- Rate limiting or credit exhaustion — returns 429 or equivalent if credits are depleted
- Malformed key path — invalid key name in URL returns 400

## 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 (client-side encrypted) value associated with the requested key within the caller's wallet-namespaced store. The response includes the raw stored payload which the client SDK decrypts locally. If the key does not exist or the namespace does not match, an error response is returned. The $0.003 USDC fee is deducted via x402 payment on each successful call.

## 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-key-get-f58982f6/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)