# ManyLives Bank Reconciliation

> ManyLives Bank Reconciliation is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-13).

Matches bank transaction rows against invoices to identify paid, unpaid, unmatched, and ambiguous entries

## Facts

- Endpoint: POST https://api.manylives.me/paid/data/reconcile?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-bank-reconciliation-2fbb1f5f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iWi9zGSi73aO8UF_z5nwk

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 manylives-bank-reconciliation-2fbb1f5f -d '<json body>'
```

Example prompt: Can you reconcile my bank statement against my outstanding invoices? Here are my bank rows — date 2026-10-03 amount 1200 description PAYMENT INV-1042, and date 2026-10-04 amount 880.25 description TRANSFER — and my invoices: INV-1042 for $1200 dated 2026-09-20, INV-1043 for $880.25 dated 2026-09-21, INV-1044 for $500 dated 2026-09-22. Use a 60-day window and allow combined payments, these are receivables.

## When to prefer this

Use this endpoint when you need automated bank-to-invoice reconciliation without setting up accounting software — especially useful in AI agent workflows for bookkeeping automation, accounts receivable/payable checks, or month-end close routines. It handles fee deductions, combined payments, and configurable date windows. Pay-per-call with no account required makes it ideal for occasional or ad-hoc reconciliation tasks.

## Known failure modes

- Malformed bank or invoice JSON causes a 400 error
- Invoice and bank data in different currencies not explicitly handled
- Very large datasets may time out
- Ambiguous matches returned without resolution when multiple invoices could fit a payment
- Payments arriving outside the date_window_days threshold will not be matched

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

A JSON object with totals (unpaid, matched, unmatched_bank amounts), an array of matched entries with the rule used and matched invoice numbers, an array of ambiguous bank rows with candidate invoices, an array of unmatched bank rows, and an array of unpaid invoices.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bank": {
   "type": "string",
   "examples": [
    [
     {
      "date": "2026-10-03",
      "amount": 1200,
      "description": "PAYMENT INV-1042"
     },
     {
      "date": "2026-10-04",
      "amount": 880.25,
      "description": "TRANSFER"
     }
    ]
   ],
   "description": "bank rows [{date, description, amount}] or bank_csv"
  },
  "fee_pct": {
   "type": "string",
   "description": "optional card or platform fee taken from payments, e.g. 1.75"
  },
  "invoices": {
   "type": "string",
   "examples": [
    [
     {
      "date": "2026-09-20",
      "amount": 1200,
      "number": "INV-1042"
     },
     {
      "date": "2026-09-21",
      "amount": 880.25,
      "number": "INV-1043"
     },
     {
      "date": "2026-09-22",
      "amount": 500,
      "number": "INV-1044"
     }
    ]
   ],
   "description": "invoices [{number, amount, date}] or invoices_csv"
  },
  "direction": {
   "type": "string",
   "description": "optional receivables (default: money in, positive amounts) or payables (money out)"
  },
  "allow_combined": {
   "type": "string",
   "description": "optional true (default) to match one payment to two invoices"
  },
  "date_window_days": {
   "type": "string",
   "description": "optional days after the invoice date a payment can arrive (default 60)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "totals": {
   "unpaid": 880,
   "matched": 1200,
   "unmatched_bank": 45.5
  },
  "matched": [
   {
    "date": "2026-10-03",
    "rule": "invoice number in the reference",
    "amount": 1200,
    "bank_row": 1,
    "invoices": [
     "INV-1042"
    ]
   }
  ],
  "ambiguous": [
   {
    "amount": 300,
    "bank_row": 4,
    "candidates": [
     "INV-1050",
     "INV-1051"
    ]
   }
  ],
  "unmatched_bank": [
   {
    "amount": 45.5,
    "bank_row": 6,
    "description": "TRANSFER"
   }
  ],
  "unpaid_invoices": [
   {
    "date": "2026-09-12",
    "amount": 880,
    "number": "INV-1047"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-bank-reconciliation-2fbb1f5f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)