# AgentKV Read (GET) — Encrypted Key-Value Lookup

> AgentKV Read (GET) — Encrypted Key-Value Lookup 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 the agent-native encrypted key-value store for a specific key, billed per-request via x402 micropayment with no API key required.

## Facts

- Endpoint: GET https://api.agentx402.ai/v1/kv/canary-kv-1785255879
- 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-encrypted-key-value-lookup-6621af46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Esf3fCT8fyjbgj8tGnV1m

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-encrypted-key-value-lookup-6621af46
```

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

## When to prefer this

Choose this endpoint when an AI agent needs lightweight, pay-per-use persistent memory without any signup, API key management, or traditional account infrastructure. It is ideal for stateless agents that need to recall previously written values (configs, credentials, session state) using only a crypto wallet for identity and payment. Prefer it over traditional KV stores when the agent operates in a trustless, x402-enabled environment and encryption at rest is required by default.

## Known failure modes

- Key not found — returns 404 if the key has never been written or has been deleted
- Insufficient credits — payment rejected if wallet has no balance and no prepaid credits remain
- Invalid key path — malformed or unauthorized key returns 400 or 403
- Payment failure — x402 micropayment not processed, request blocked
- Namespace mismatch — accessing a key outside the caller's wallet namespace returns 403

## 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 client-side encrypted value stored at the requested key within the caller's wallet-namespaced partition. The response contains the raw (encrypted) payload that was previously written to that key, which the client can decrypt locally. If the key does not exist, an appropriate not-found response is returned.

## 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-encrypted-key-value-lookup-6621af46/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)