Detect letter of credit discrepancies API

Compare supplied LC terms with linked invoices and documents. Missing required document types are flagged only from the LC list.

The Detect letter of credit discrepancies operation is part of the Trade Finance & Receivables Intelligence API on BRAINIAC.software. Compare supplied LC terms with linked invoices and documents. Missing required document types are flagged only from the LC list. It is exposed as POST /api/v1/trade-finance/letter-of-credit-discrepancy-detect and priced at $0.06 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied invoices, contracts, letters of credit, and trade documents World Bank Open Data (no API key) when requested Limitations: No paid trade-finance data provider is used and no API key is required. Missing amounts, parties, and due dates are not invented. Financing readiness and discounting are descriptive only. A credit or financing decision is never produced. Discrepancy checks compare supplied fields only and do not contact banks or registries. World Bank responses are contextual only when country and indicator codes are supplied. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Match trade finance documents, Assess invoice financing readiness, Analyze receivable aging risk, Detect invoice assignment conflicts. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.06 USDC
/api/v1/trade-finance/letter-of-credit-discrepancy-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/trade-finance/letter-of-credit-discrepancy-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "lettersOfCredit": [
    {
      "id": "LC-1",
      "number": "LC-77",
      "issueDate": "2026-08-15",
      "expiryDate": "2026-11-30",
      "currency": "USD",
      "amount": 100000,
      "applicant": "Buyer Co",
      "beneficiary": "Seller Co",
      "goods": "Widgets",
      "latestShipment": "2026-09-30",
      "requiredDocs": [
        "bill of lading",
        "packing list"
      ]
    }
  ],
  "invoices": [
    {
      "id": "INV-1",
      "number": "INV-1001",
      "issueDate": "2026-09-01",
      "currency": "USD",
      "amount": 105000,
      "buyer": "Buyer Co",
      "seller": "Seller Co",
      "goods": "Gadgets",
      "lcId": "LC-1"
    }
  ],
  "documents": [
    {
      "id": "DOC-1",
      "type": "bill of lading",
      "number": "BL-1",
      "date": "2026-10-05",
      "currency": "USD",
      "amount": 105000,
      "shipper": "Seller Co",
      "consignee": "Buyer Co",
      "lcId": "LC-1"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Trade Finance & Receivables Intelligence APIFull docsHow it works