Gumloop vs Cooper (Mandl)

Gumloop

Gumloop's REST API has a public OpenAPI file with 105 operations, Markdown docs and a changelog with 28 dated releases since 9 July 2026. API keys need the $37 Pro plan, the trial needs a card, the key can travel in the URL, and self-serve content may be used to train Gumloop's models.

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.

Gumloop

1. Send the key as Authorization: Bearer and, for a personal key, add the x-auth-key header with the user ID. Do not put api_key in the URL
2. Create sessions with POST /agents/{agent_id}/sessions, then poll GET /sessions/{session_id}. A 202 means processing or queued, and the reply is not in the response
3. Supply your own session_id when creating a session. A repeat returns 409, which makes a retry safe
4. For streamed output send the same body with stream: true to ws.gumloop.com. api.gumloop.com answers 400 to it
5. Treat a webhook trigger URL as a password. It returns {"success": true} at once and never carries the agent's output

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