Authenticate to the AMS or carrier API (e.g., Applied Epic, Vertafore AMS360, or a carrier COI issuance endpoint)
Validate the requested certificate holder name and address against the insured's active policy endorsements to determine if a new additional insured endorsement is required
If an additional insured endorsement is needed, trigger the endorsement request workflow before issuing the certificate
Construct the certificate issuance request: policy numbers, coverage types, limits, effective dates, description of operations, and certificate holder details
Submit the request and receive the generated ACORD 25 (Liability) or ACORD 27/28 (Property) certificate PDF
Deliver the certificate to the requestor via email API or a certificate holder notification service and store a copy in the document management system
Known gotchas
COIs may not be altered by agents or insureds to show coverage that does not exist on the policy; validate that the requested limits and coverages match the in-force policy before generating the certificate
Some states have regulations prohibiting the issuance of certificates that include language not supported by the underlying policy; implement a compliance check for non-standard descriptions of operations
Auto-issuance workflows that bypass underwriter review for additional insured endorsements can inadvertently grant broader coverage than intended; route non-standard AI requests for review
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