The 2026 AI-Readiness Buyer Checklist for Insurance CRMs (15 Questions Every Agency Should Ask)

Before you sign another insurance CRM contract, run vendors through this 15-question MCP and API readiness checklist.

Key Takeaways

  • 15 questions covering API, MCP, webhooks, discovery, security
  • Score 13+ = safe; under 9 = walk away
  • Most insurance CRMs score 0–4 today

The CRMs being signed in 2026 will need to be agent-ready. The CRMs being unwound in 2027 will be the ones that weren't. Here's the buyer checklist.

API Foundation

  1. Do you publish a live OpenAPI 3.1 spec at a public URL?
  2. Is the spec generated from code, or hand-maintained?
  3. Is it versioned via X-Api-Version header on every response?
  4. Are bulk operations supported on every collection?

MCP & Agent Compatibility

  1. Do you ship a native MCP server?
  2. How many MCP tools are exposed (and across what resources)?
  3. Do API and MCP credentials share the same key surface?
  4. What MCP clients do you officially test against (Claude, Cursor, Continue, etc.)?

Webhooks & Event Streaming

  1. Are webhook payloads HMAC-signed?
  2. Is there a documented retry ladder and dead-letter queue?
  3. Are webhook subscriptions per-event-type with rotatable secrets?

Discovery & Observability

  1. Do you publish llms.txt, llms-full.txt, and AgentSkills manifest?
  2. Are there public /health and /whoami endpoints?
  3. Does every response carry an X-Request-Id for support tracing?

Security & Scoping

  1. Can API keys be scoped to specific resources and operations?

Scoring

13–15 yeses: Buy with confidence. 9–12: Get a written roadmap commitment. Under 9: Walk. The 18 months it takes them to catch up will cost you more than switching now.

Where This Fits In unLocked