{"id":"openapi-31-insurance-crm","slug":"openapi-31-spec-insurance-crm-importance","title":"Why a Live OpenAPI 3.1 Spec Is Now a Buying Criterion for Insurance CRMs","excerpt":"Static PDF API docs are dead. Here's why agencies — and the AI tools they're adopting — now demand a machine-readable, always-current OpenAPI 3.1 spec.","content":"<p>For two decades, \"API documentation\" meant a PDF or a confluence page that drifted out of sync with reality the day after it was published. Modern AI tooling has killed that pattern.</p>\n\n<h2>The Shift</h2>\n<p>ChatGPT Custom GPTs ingest OpenAPI specs to auto-generate Actions. Postman and Insomnia import OpenAPI to seed collections. Stainless, Speakeasy, and Fern generate typed SDKs from OpenAPI. Cursor and Claude can reference OpenAPI to ground tool calls. Without a live, versioned OpenAPI 3.1 document, your CRM is invisible to all of these.</p>\n\n<h2>Why 3.1 Specifically</h2>\n<p>OpenAPI 3.1 is fully aligned with JSON Schema 2020-12, supports nullable types properly, and adds the <code>webhooks</code> object for documenting outbound events alongside inbound endpoints. Earlier versions force ugly workarounds.</p>\n\n<h2>What \"Live\" Means</h2>\n<p>The spec must be served from the same deployment as the API itself, generated from code (not hand-maintained), and updated on every deploy. unLocked CRM ships its OpenAPI 3.1 doc from an Edge Function that introspects the route table at request time — drift is structurally impossible.</p>\n\n<h2>Buying Checklist</h2>\n<ul>\n<li>Public OpenAPI 3.1 URL (not gated behind login)</li>\n<li>Versioned via <code>X-Api-Version</code> header</li>\n<li>Includes the <code>webhooks</code> object</li>\n<li>Imports cleanly into Postman, ChatGPT Custom GPTs, and Stainless</li>\n</ul>","category":"Strategy","featureLink":"/mcp-server","cluster":"mcp-api","date":"2026-11-18","lastModified":"2026-11-18","readTime":"5 min","author":"unLocked Team"}