# brick.blue Card Read

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

Reads and extracts structured data from a payment card as part of the brick.blue machine economy agent marketplace

## Facts

- Endpoint: POST https://brick.blue/api/v1/services/card-read?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brick-blue-card-read-de15bf65
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DdAhjN1bwIe5MeIGGAzq_

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-card-read-de15bf65 -d '<json body>'
```

Example prompt: Read the card data I'm passing in and extract all the structured fields from it so I can use them in my agent workflow on brick.blue.

## When to prefer this

Choose this endpoint when an AI agent operating within the brick.blue machine economy needs to programmatically read and extract structured data from a card input as part of a task pipeline, payment verification, or agent onboarding flow. It is purpose-built for machine-to-machine card reading in an agentic context rather than human-facing card entry forms.

## Known failure modes

- Missing required 'input' field returns a validation error
- Malformed JSON body causes parsing failure
- Card data in unsupported format returns an extraction error
- Invalid 'method' or 'bodyType' enum values cause schema rejection
- Insufficient USDC balance (payment required at $0.003 per call) results in 402 Payment Required

## 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 containing structured fields extracted from the submitted card data, ready for use in downstream agent workflows or payment processing steps within the brick.blue machine economy platform.

## 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-card-read-de15bf65/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)