Obtain API access credentials from the MGA's developer portal and review the submission data requirements for the target program (e.g., habitational, professional liability, cyber)
Map the insured's application data to the MGA's submission schema, including program-specific fields that differ from standard ACORD forms
Submit the application and receive an indicative quote response with premium, coverage terms, and any subjectivities required before binding
Collect and upload supporting documents required by the MGA (loss runs, applications, financials) via the document upload endpoint
If the quote is accepted, submit the bind request referencing the quote ID and confirm the bound policy number and coverage effective date
Retrieve the issued policy documents from the MGA's document API and store them in the client record
Known gotchas
MGA APIs often expose a subset of the carrier's full rating logic; certain risk characteristics may trigger manual underwriter review even if the API accepts the submission without error
Program appetite changes frequently; an API that accepted a risk last month may return a decline today due to a capacity change or underwriting guideline update that was not reflected in API documentation
Binding through an MGA API on behalf of a client requires the agent to have the appropriate license and binding authority agreement in place; do not automate binding without verifying authority
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