Cooper (Mandl) vs Microsoft Power Automate

Cooper (Mandl)

Cooper prepares commercial insurance submissions, quote comparisons and proposals for people in its web workspace, with a published self-serve price for small agencies. It has no API, MCP server or webhooks for an outside agent, and its SOC 2 and HIPAA claims come with no report and apply only to full Cooper.

Microsoft Power Automate

Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.

Cooper (Mandl)

1. Don't plan to call Cooper from another agent. It's operated by people in its web workspace
2. If a user's agency uses Cooper, hand them the account documents to forward to Cooper themselves
3. Don't send client insurance data or PHI to Cooper without the agency's signed agreement and, for PHI, a business associate agreement

Microsoft Power Automate

1. Filter workflows on category eq 5 for cloud flows, and add $select, because clientdata holds the whole definition
2. Flows created through the API start with statecode 0 (off). The docs say to turn the flow on before use
3. Put the flow in a solution first. Flows that sit only under My flows are outside the supported API
4. On 429 wait the Retry-After seconds. Reads of flowruns count against the daily Power Platform request allowance
5. Treat an HTTP trigger URL with sig= as a secret, and prefer the tenant or named-user trigger modes with a bearer token for https://service.flow.microsoft.com/