List available benefits for the employer using GET /employer/benefits to retrieve benefit IDs, types, and descriptions supported by the connected payroll provider.
Retrieve the current enrollment status for an individual using GET /employer/benefits/{benefit_id}/enrolled-individuals to check whether the employee is already enrolled.
Enroll the employee by sending a POST to /employer/benefits/{benefit_id}/individuals with the individual_id and contribution object specifying type (fixed or percent) and amount.
Confirm enrollment by re-fetching GET /employer/benefits/{benefit_id}/enrolled-individuals and verifying the employee appears with the correct contribution.
Handle provider-specific limitations by checking the features field on the benefit object — not all providers support all contribution types via Finch.
Known gotchas
Finch's benefits write API has limited provider coverage — many payroll providers only support read operations for benefits; always check the Finch provider capability matrix before attempting writes.
Contribution amounts are submitted in cents (integer) for fixed types; submitting a decimal or a dollar amount will cause a validation error or silent mis-entry.
Finch is a passthrough layer — if the underlying provider has deduction code or plan setup requirements (like ADP), those must be fulfilled in the provider UI first.
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