# BRAINIAC Accounts Payable Purchase Order Match

> BRAINIAC Accounts Payable Purchase Order Match is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.06/call, status unknown (last checked 2026-11-17).

Compares an invoice against a purchase order (provided as structured data or a document file) and reports line-by-line match status, mismatches, and findings.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/accounts-payable/purchase-order-match?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-accounts-payable-purchase-order-match-dc381c7b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_imCmWHa3RDnumu6Umydwl

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-accounts-payable-purchase-order-match-dc381c7b -d '<json body>'
```

Example prompt: Can you check whether this invoice from our supplier matches our purchase order? The invoice is for PO-55, with two lines: 'Paper ream' (SKU RM-1, qty 1, $10) and 'Ink cartridge' (SKU INK-2, qty 3, $90). The PO has the same items but ink cartridges at qty 1, $30. Tell me if everything lines up or flag any mismatches.

## When to prefer this

Use this endpoint when you need a lightweight, no-account, pay-per-call invoice-to-PO reconciliation without setting up a full AP platform. Ideal for agents automating accounts payable workflows, flagging discrepancies before payment approval, or auditing supplier invoices on demand. Prefer it over manual review or heavier ERP integrations when you need a fast, structured match result with line-level detail for a single invoice.

## Known failure modes

- Invoice lines reference SKUs not present in the PO — reported as unmatched lines
- Description-only matching (no SKU) may fail if names differ even slightly
- File too large or unsupported media type returns an error
- Missing required invoice fields cause validation failure
- Truncated or malformed base64 file content causes processing error
- Currency mismatches between invoice and PO are flagged but not auto-converted

## 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 an overall match status ('matched' or 'mismatch'), a per-line breakdown showing each line's SKU, description, source, status (matched/mismatch), and detail message, plus a findings array listing specific discrepancy codes (e.g. po_line_mismatch) with severity and human-readable detail, the PO number, the timestamp of the check, a paymentInitiated flag (always false), and a limitations list clarifying what was and was not checked.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "application/pdf",
      "text/plain",
      "text/csv"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "invoice": {
   "type": "object",
   "properties": {
    "tax": {
     "type": "number",
     "maximum": 1000000000000,
     "minimum": -1000000000000
    },
    "lines": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "description"
      ],
      "properties": {
       "sku": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1
       },
       "tax": {
        "type": "number",
        "maximum": 1000000000000,
        "minimum": -1000000000000
       },
       "amount": {
        "type": "number",
        "maximum": 1000000000000,
        "minimum": -1000000000000
       },
       "quantity": {
        "type": "number",
        "maximum": 1000000000,
        "minimum": -1000000000
       },
       "unitPrice": {
        "type": "number",
        "maximum": 1000000000000,
        "minimum": -1000000000000
       },
       "description": {
        "type": "string",
        "maxLength": 300,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     "maxItems": 200
    },
    "total": {
     "type": "number",
     "maximum": 1000000000000,
     "minimum": -1000000000000
    },
    "dueDate": {
     "type": "string",
     "format": "date",
     "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    },
    "taxRate": {
     "type": "number",
     "maximum": 100,
     "minimum": 0
    },
    "currency": {
     "type": "string",
     "pattern": "^[A-Za-z]{3}$"
    },
    "discount": {
     "type": "number",
     "maximum": 1000000000000,
     "minimum": -1000000000000
    },
    "poNumber": {
     "type": "string",
     "maxLength": 80,
     "minLength": 1
    },
    "shipping": {
     "type": "number",
     "maximum": 1000000000000,
     "minimum": -1000000000000
    },
    "subtotal": {
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "lines": [
   {
    "sku": "RM-1",
    "detail": "The description and the numbers present on both sides agree.",
    "source": "invoice",
    "status": "matched",
    "description": "Paper ream"
   },
   {
    "sku": "INK-2",
    "detail": "The purchase-order line was found, but quantity 3 does not match 1; amount 90.00 does not match 30.00.",
    "source": "invoice",
    "status": "mismatch",
    "description": "Ink cartridge"
   }
  ],
  "status": "mismatch",
  "findings": [
   {
    "code": "po_line_mismatch",
    "detail": "The invoice line \"Ink cartridge\" does not match the purchase order: quantity 3 does not match 1; amount 90.00 does not match 30.00.",
    "severity": "error"
   }
  ],
  "poNumber": "PO-55",
  "checkedAt": "2026-11-02T19:00:00.000Z",
  "limitations": [
   "No payment was initiated.",
   "Tax rules, purchase orders, supplier records, and payment terms are not invented when they are absent.",
   "Only the invoice, purchase order, and prior invoices in this request are compared.",
   "Purchase-order lines match on SKU when both sides have one, otherwise on the same description. Similar names are not matched."
  ],
  "paymentInitiated": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-accounts-payable-purchase-order-match-dc381c7b/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)
