# agentbit.app Key-Value Memory

> agentbit.app Key-Value Memory is a paid API for AI agents from agentbit.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-13).

Persistent private key-value store for agents: set, get, delete, check existence, or list stored values scoped to the paying wallet.

## Facts

- Endpoint: POST https://agentbit.app/v1/memory?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-app-key-value-memory-9e36191b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2OLge-S-aCL6Tkd_MbZ8x

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 agentbit-app-key-value-memory-9e36191b -d '<json body>'
```

Example prompt: Store the value 'premium' under the key 'user_tier' in the 'subscriptions' namespace, and set it to expire in 3600 seconds.

## When to prefer this

Use this endpoint when an AI agent needs lightweight persistent state or memory across calls — session flags, user preferences, cached results, or workflow checkpoints — scoped privately to the paying wallet. Prefer it over in-context memory when data must survive across sessions, and over full databases when simplicity and per-call pricing are priorities.

## Known failure modes

- Key not found on 'get' or 'delete' returns null or 404-style result
- Missing required 'key' field for set/get/delete/exists operations returns validation error
- Missing required 'value' field for 'set' operation returns validation error
- TTL exceeding 90 days is clamped or rejected
- Invalid operation enum value returns an error
- Payment failure or insufficient balance blocks the call

## How this service works

Private key/value memory for an agent: remember values across calls (set/get/delete/list/exists), scoped to the paying wallet.

## Output

Returns a JSON object containing the operation result: for 'get', the stored value; for 'exists', a boolean; for 'list', an array of keys up to the specified limit; for 'set' and 'delete', a confirmation of success. Data is scoped to the paying wallet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "description": "The key (required for set/get/delete/exists)."
  },
  "limit": {
   "type": "integer",
   "description": "For list: max keys to return (default 100, max 500)."
  },
  "value": {
   "description": "Any JSON value to store (required for set)."
  },
  "namespace": {
   "type": "string",
   "description": "Optional group for keys (default \"default\")."
  },
  "operation": {
   "enum": [
    "set",
    "get",
    "delete",
    "exists",
    "list"
   ],
   "type": "string",
   "description": "What to do."
  },
  "ttl_seconds": {
   "type": "integer",
   "description": "Optional expiry in seconds (default 30 days, max 90; 0 = no expiry)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-app-key-value-memory-9e36191b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentbit.app](https://www.zero.xyz/host/agentbit.app/llms.txt)