# Baby Blue Viper Agent Memory Store

> Baby Blue Viper Agent Memory Store is a paid API for AI agents from api.babyblueviper.com, paid per call via x402, $0.039031/call, status unknown (last checked 2026-09-15).

Stores a key-value memory entry for an autonomous agent, namespaced by the paying Lightning/x402 wallet, with per-call micropayment via x402 or Bearer token.

## Facts

- Endpoint: POST https://api.babyblueviper.com/memory/store
- Price: $0.039031/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/baby-blue-viper-agent-memory-store-896ea611
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dF7zxoR1BNxeX8uOQHAoy

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 baby-blue-viper-agent-memory-store-896ea611 -d '<json body>'
```

Example prompt: Save my current agent state to Baby Blue Viper memory under the key 'session_context' with the value 'step=3,goal=buy_BTC,confidence=0.87' — pay for it from my x402 wallet.

## When to prefer this

Use this endpoint when an autonomous agent or trading bot needs to persist state or context between invocations in a Lightning-native, wallet-namespaced key-value store, especially when operating within the Baby Blue Viper agent ecosystem and paying via x402 USDC or Bearer token micropayments. Prefer this over generic key-value stores when wallet-derived namespacing and per-call micropayment are acceptable or desired.

## Known failure modes

- Payment failure — x402 or Bearer token invalid or insufficient funds, returns 402 Payment Required
- Key too long — key exceeds 100 characters, returns 400 Bad Request
- Value too large — value exceeds 200 KB, returns 413 Payload Too Large
- Missing key or value — required fields absent, returns 400 Bad Request
- Wallet/namespace not resolvable — wallet address cannot be derived from payment credentials, returns 401 Unauthorized

## How this service works

A neutral verdict before an irreversible action, a signed proof after, and a public track record of being right you recompute — not a score you trust. The verdict is provably committed before the outcome it's graded against: no TEE, no trusted scorer.

## Output

Returns a JSON object confirming the stored key, a 'stored' status, the agent_id derived from the paying wallet (e.g. x402:0xabc…), the cost in satoshis, and the size in bytes of the stored value.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "description": "Memory key (1-100 chars)"
  },
  "value": {
   "type": "string",
   "description": "Memory value (up to 200 KB)"
  },
  "agent_id": {
   "type": "string",
   "description": "Ignored on x402 path; namespace is derived from paying wallet"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "key": "state",
  "status": "stored",
  "agent_id": "x402:0xabc…",
  "cost_sats": 50,
  "size_bytes": 512
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/baby-blue-viper-agent-memory-store-896ea611/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.babyblueviper.com](https://www.zero.xyz/host/api.babyblueviper.com/llms.txt)