Query GET /transactions with account_id, created_at[gte], and created_at[lte] covering your close period; page through all results using the cursor parameter until the next_cursor in the response is null
Separately retrieve GET /account_statements filtered by account_id and statement_period to get official statement objects for the same period; compare the statement's beginning_balance and ending_balance to your GL opening and closing balances
For each transaction, extract the id, amount, currency, created_at, description, and route_id (the underlying payment rail object ID such as an ACH transfer or wire transfer ID)
Enrich each transaction by fetching the route object (e.g., GET /ach_transfers/{id}) using the route_id to obtain full payment details including counterparty, SEC code, and trace number for ACH
Build a period reconciliation: starting balance + sum of credits - sum of debits = ending balance; any discrepancy indicates either a missing transaction page or a timing difference on pending items
Export the reconciled dataset to your accounting system with the Increase transaction ID as the external reference for idempotent re-import
Known gotchas
Increase uses cursor-based pagination, not page-number pagination; always capture the next_cursor from the response and use it in the next request — reconstructing a cursor or assuming page size is not supported
Pending transactions (for real-time payment rails) may appear in the transaction list before final settlement; filter by status=complete for period-close reconciliation to avoid counting unsettled items
The created_at timestamp on a transaction reflects when Increase recorded it, which may differ from the bank's value date for wires; use the route object's settlement timestamp for bank-date reconciliation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp