# BRAINIAC Trade Finance Document Party Consistency Checker

> BRAINIAC Trade Finance Document Party Consistency Checker 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).

Checks that buyer, seller, shipper, and other named parties are consistent across invoices, contracts, letters of credit, and trade documents, flagging any mismatches or conflicts.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/trade-finance/document-party-consistency?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-trade-finance-document-party-consistency-checker-2cda4e20
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mw33_oQ6CX4lVPFiwnTlz

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-trade-finance-document-party-consistency-checker-2cda4e20 -d '<json body>'
```

Example prompt: Check whether the buyer, seller, and shipper names are consistent across these trade documents — I have invoice INV-001 showing 'Acme Corp' as seller and a bill of lading showing 'Acme Corporation' as shipper, plus the letter of credit naming 'Acme Corp', and I need to know if there are any party conflicts before we submit for financing.

## When to prefer this

Use this endpoint when you need automated, structured detection of party name mismatches across trade finance documents (invoices, contracts, letters of credit, bills of lading) — particularly before submitting a trade finance package for discounting or financing. Prefer this over manual review or generic document comparison when you need machine-readable conflict codes and a structured findings array. It does not require an API key or account, charges a flat $0.04 USDC per call via x402, and explicitly avoids inventing data or making credit decisions, making it suitable for compliance audit trails.

## Known failure modes

- Missing required party or invoice fields result in fewer checks being performed rather than an error
- Inconsistent name spellings (e.g. abbreviations) may produce false-positive conflicts
- Truncated input due to maxLength limits may cause incomplete party comparisons
- If no invoices or documents are supplied, the check count will be zero with no meaningful findings
- Ambiguous role assignments across parties can lead to inconclusive consistency results

## 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 checked invoice items, each showing buyer, seller, conflict details (field name and description), check count, and whether the document set is consistent. Also returns a findings array with structured discrepancy codes, a summary of consistent vs conflicting invoices, public sources used, and a set of limitations clarifying that no financing decisions or invented data are produced.

## 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
  },
  "parties": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "name": {
      "type": "string",
      "maxLength": 200
     },
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "country": {
      "type": "string",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "maxItems": 200
  },
  "invoices": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "lcId": {
      "type": "string",
      "maxLength": 80
     },
     "buyer": {
      "type": "string",
      "maxLength": 200
     },
     "goods": {
      "type": "string",
      "maxLength": 400
     },
     "amount": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": 0
     },
     "number": {
      "type": "string",
      "maxLength": 80
     },
     "seller": {
      "type": "string",
      "maxLength": 200
     },
     "source": {
      "type": "string",
      "maxLength": 160
     },
     "status": {
      "type": "string",
      "maxLength": 80
     },
     "country": {
      "type": "string",
      "maxLength": 80
     },
     "dueDate": {
      "type": "string",
      "maxLength": 40
     },
     "currency": {
      "type": "string",
      "maxLength": 12
     },
     "incoterm": {
      "type": "string",
      "maxLength": 40
     },
     "issueDate": {
      "type": "string",
      "maxLength": 40
     },
     "contractId": {
      "type": "string",
      "maxLength": 80
     },
     "outstanding": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": 0
     },
     "pay
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "buyer": "Buyer Co",
    "seller": "Seller Co",
    "conflicts": [
     {
      "field": "shipper_DOC-1",
      "detail": "Invoice seller vs document shipper DOC-1"
     }
    ],
    "invoiceId": "INV-1",
    "checkCount": 6,
    "consistent": false,
    "conflictCount": 1,
    "amountInvented": false,
    "creditDecision": false,
    "financingApproved": false
   }
  ],
  "status": "checked",
  "findings": [
   {
    "code": "shipper_DOC-1",
    "kind": "conflict",
    "detail": "Invoice seller vs document shipper DOC-1 do not match.",
    "subject": "INV-1"
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "limitations": [
   "Invoices, contracts, letters of credit, trade documents, and assignments are copied only from labeled fields supplied by the caller, or from key-free public World Bank trade responses when requested.",
   "No paid trade-finance data provider is used and no API key is required.",
   "Missing amounts, due dates, parties, and document fields are not invented.",
   "Financing readiness and discounting figures are descriptive calculations only. A credit or financing decision is never produced.",
   "Discrepancy and conflict findings compare supplied fields only and do not contact banks or registries."
  ],
  "invoiceCount": 1,
  "publicSources": [],
  "amountInvented": false,
  "apiKeyRequired": false,
  "creditDecision": false,
  "consistentCount": 0,
  "paidProviderUsed": false,
  "financingApproved": false,
  "discrepancyInvented": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-trade-finance-document-party-consistency-checker-2cda4e20/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)
