# BRAINIAC Payment Intelligence — Transaction Categorization Correction

> BRAINIAC Payment Intelligence — Transaction Categorization Correction is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).

Applies caller-supplied category corrections to a set of financial transactions and returns which corrections were matched and applied

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/payment-intelligence/transaction-categorization-correct?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-payment-intelligence-transaction-categorization-correction-58aaf8b2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_b9dzQnNwDHKLFAKpBYHmv

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 brainiac-payment-intelligence-transaction-categorization-correction-58aaf8b2 -d '<json body>'
```

Example prompt: I have a list of transactions exported from my bank and Netflix keeps getting categorized as 'entertainment' instead of 'subscription' — can you apply a correction so transaction TX-1001 gets reclassified from 'entertainment' to 'subscription' for merchant Netflix, and tell me which corrections were actually applied?

## When to prefer this

Use this endpoint when you have a set of financial transactions and a known list of category corrections to apply — especially when correcting miscategorized merchants like subscriptions mislabeled as entertainment, or when you need an audit trail of which corrections were matched and applied. Prefer this over a general categorization endpoint when you already know the correct categories and just need them enforced against existing data. It is well-suited for fintech agents, personal finance tools, and accounting workflows that accumulate correction rules over time.

## Known failure modes

- Corrections not matched if transaction IDs or merchant names don't align with supplied data
- Truncated input if CSV/JSON exceeds 200,000 character limit
- Missing transactions if data is supplied in an unsupported format or field
- No corrections applied if correction rules are ambiguous or empty
- 402 Payment Required if USDC payment via x402 is not completed before the call

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a list of applied corrections (each showing the from/to categories, matched merchant, matchedBy field, and whether it was applied), overall status, appliedCount, correctionCount, checkedAt timestamp, and a findings array. Also includes limitation disclosures confirming no bank connection, no invented data, and no affordability decisions were made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "accounts": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "type": {
      "type": "string",
      "maxLength": 80
     },
     "currency": {
      "type": "string",
      "maxLength": 12
     }
    },
    "additionalProperties": false
   },
   "maxItems": 100
  },
  "merchants": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "aliases": {
      "type": "array",
      "items": {
       "type": "string",
       "maxLength": 200
      },
      "maxItems": 20
     },
     "category": {
      "type": "string",
      "maxLength": 120
     }
    },
    "additionalProperties": false
   },
   "maxItems": 400
  },
  "corrections": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "to": {
      "type": "string",
      "maxLength": 120
     },
     "from": {
      "type": "string",
      "maxLength": 120
     },
     "merchant": {
      "type": "string",
      "maxLength": 200
     },
     "transactionId": {
      "type": "string",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "maxItems": 400
  },
  "transactions": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "mcc": {
      "type": "string",
      "maxLength": 20
     },
     "date": {
      "type": "string",
      "maxLength": 40
     },
     "amount": {
      "type": "n
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "to": "subscription",
    "from": "subscription",
    "applied": true,
    "merchant": "Netflix",
    "matchedBy": "transaction_id",
    "bankConnected": false,
    "transactionId": "TX-1",
    "openBankingConnected": false
   }
  ],
  "status": "corrected",
  "findings": [],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "limitations": [
   "Transactions, accounts, merchants, and category corrections are copied only from labeled fields supplied by the caller.",
   "No bank account is connected and no Open Banking credentials are required or used.",
   "Income, affordability, and merchant identity are derived only from supplied rows. Missing values are not invented.",
   "Recurring and subscription detection use date spacing and description/merchant similarity from the supplied set only.",
   "An affordability or credit decision is never produced."
  ],
  "appliedCount": 1,
  "bankConnected": false,
  "incomeInvented": false,
  "correctionCount": 1,
  "credentialsRequired": false,
  "openBankingConnected": false,
  "affordabilityDecision": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-payment-intelligence-transaction-categorization-correction-58aaf8b2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
