CageMatch.
LIVE — hitting production API + warehouse

Full pipeline against the live API.

Each upload runs the production caging-api: image is MICR-redacted server-side, OCR'd, stored to R2, and the donor is matched against our warehouse's 261M FEC records via the real warehouse-match endpoint.

Click a sample check to run it

Synthetic data for demo. Click any check below to send it through the full flow — OCR, warehouse lookup, filing-ready output.

Or upload your own

What's wired up

  1. POST api.cagematch.io/api/v1/scanner/extract/ — MICR strip is destroyed at the pixel level before OCR sees the image. Redacted image is stored in tenant-scoped R2 prefix. Account & routing numbers never persist.
  2. POST api.cagematch.io/api/v1/caging/warehouse-match/ — Tier 2 endpoint hits campaign-warehouse-api which is the single point of BigQuery access (261M FEC + 48M state records).
  3. Audit log — every warehouse match writes an audit-log row; treasurers and regulators can pull the full trail via GET /caging/audit/{committee_id}/.

Privacy contract (enforced server-side)

  • • Original image never touches disk — redacted version stored only after MICR is destroyed.
  • • Account number, routing number, bank name are not in any database, log, or returned field.
  • • Stored images are tenant-scoped: cross-tenant fetch returns 404, not 403.
  • • Signed URL TTL: 5 minutes.