# 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-14).

Reads a value from an agent-native, client-side encrypted key-value store, billed per-request via x402 micropayment with no API key required.

## Facts

- Endpoint: GET https://api.agentx402.ai/v1/kv/dev-canary-1785214805
- 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-key-get-2f1f5044
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WAEr0QliQSMxwp0wKbsBK

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-2f1f5044
```

Example prompt: Read the value stored under the key 'dev-canary-1785214805' in my AgentKV namespace — use my wallet as the namespace and pay the $0.003 read fee automatically.

## When to prefer this

Choose this endpoint when an AI agent needs to retrieve a previously stored value from a persistent, encrypted key-value store without managing API keys or signup — ideal for stateful agent workflows, inter-agent data sharing, and storing encrypted configuration or memory. Prefer over generic cloud KV stores (Redis, DynamoDB) when payment is via x402 micropayment and the namespace is automatically scoped to a wallet identity.

## Known failure modes

- Key not found (404): the requested key does not exist in the namespace
- Insufficient credits or payment failure (402): x402 payment header missing, malformed, or insufficient funds
- Namespace mismatch: wallet/account key in payment doesn't match the stored namespace
- Decryption failure: client-side encrypted value cannot be decrypted without the correct key
- Rate limiting or service unavailability (503)

## 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 in the caller's namespace (scoped to their wallet address or ak_ account key). The value was client-side encrypted at write time, so the agent receives the encrypted blob or the decrypted value depending on SDK usage. Response also includes key metadata such as existence status and last-write timestamp where available.

## 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-2f1f5044/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)