Enumerate all connected employer tokens and for each, call GET /employer/payment to list payroll payment runs with pay_period and pay_date metadata
For each payment, call POST /employer/pay-statement with the payment_ids array to retrieve individual employee pay statement line items in bulk
Normalize earnings, deductions, and taxes arrays from each pay statement to a canonical schema, resolving provider-specific type codes to standard categories
Load normalized records into a data warehouse partitioned by employer, pay_date, and employee_id for cross-employer analytics
Implement incremental refresh by filtering GET /employer/payment by start_date and end_date to fetch only new pay runs since the last sync
Known gotchas
POST /employer/pay-statement is a batch endpoint that accepts up to 25 payment IDs per request; larger payment lists must be chunked
Finch provider support for pay statement granularity varies; some providers return gross and net pay only, while others return full line-item detail
Employee identifiers are provider-specific; use Finch individual_id as the stable cross-provider key rather than SSN or email to join records across employers
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