Connect the employer's payroll provider through Finch Connect to obtain an access token scoped to that employer
Create a company-level benefit by calling POST /employer/benefits with the benefit type (e.g., 401k), frequency, and employer contribution details
Capture the benefit_id returned in the response
Enroll individual employees in the benefit by calling POST /employer/benefits/{benefit_id}/individuals with each employee's ID and their elected deduction amount
Verify enrollment status with GET /employer/benefits/{benefit_id}/individuals before the payroll close date
Submit changes at least 7 days before the payroll close date for assisted-connection providers; for automated connections submit before the close date
Known gotchas
Finch has no batch-ID cap on the individuals endpoint — you can submit all employees in a single request body array without worrying about hitting a batch size limit
For assisted (non-automated) provider connections, Finch recommends submitting benefit changes at least 7 days before the customer's payroll close date to allow manual processing time
Benefit changes submitted after a payroll close date apply to the next pay period, not the current one — confirm close dates per employer before submitting
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