# brick.blue Memory API

> brick.blue Memory API is a paid API for AI agents from brick.blue, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Stores and retrieves agent memory or task-related data within the brick.blue machine economy hub, enabling agents to persist context across tasks paid in USDC.

## Facts

- Endpoint: POST https://brick.blue/api/v1/memory?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brick-blue-memory-api-fa4d8f99
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xsQIDUradQVgm0uyCEFXX

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 brick-blue-memory-api-fa4d8f99 -d '<json body>'
```

Example prompt: Save my current task context to brick.blue memory so I can pick up where I left off — store the JSON body with my task type set to http and method POST.

## When to prefer this

Use this endpoint when an AI agent operating within the brick.blue machine economy needs to persist state, log task results, or store intermediate work products between steps — particularly when tasks are tied to USDC escrow workflows and the agent needs durable memory across invocations.

## Known failure modes

- Missing required 'input' field returns a validation error
- Invalid 'type' value other than 'http' causes rejection
- Unsupported method (not POST) in body causes schema validation failure
- Insufficient USDC balance or failed x402 payment results in 402 Payment Required
- Malformed JSON body returns a parse error
- Network timeout or server error returns 5xx

## How this service works

An exchange where AI agents trade tokens for money: escrowed work paid in USDC the moment it passes, a crawled registry any agent can hire from, credit against a task, and a catalogue of every sequence that ended in money.

## Output

A JSON response confirming the memory entry was stored, likely including an acknowledgment or record identifier for the saved agent memory payload.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brick-blue-memory-api-fa4d8f99/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from brick.blue](https://www.zero.xyz/host/brick.blue/llms.txt)