unLocked CRM Developer Portal: Search Engines, AI Assistants, and Developers.
unLocked CRM publishes its product, pricing, carrier, integration, and competitive context in standard, crawlable formats. Every machine-readable resource is indexed here, grouped by who reads it.
The API
REST access to contacts, messaging, quoting, underwriting, and links, with the spec in three formats and every error as JSON.
API reference
HTMLAuthentication, the endpoint, list parameters, webhooks, errors, and the MCP server.
/apiopenapi.json
OpenAPI 3.1, JSONThe full spec: every endpoint, security scheme, and scope. Import it into Postman or generate a client.
/openapi.json.well-known/openapi.json
OpenAPI 3.1, JSONThe slim public subset with unique operationIds and typed parameters. Also at /api/openapi.json.
/.well-known/openapi.jsonopenapi.yaml
OpenAPI 3.1, YAMLThe public spec in YAML. A Swagger 2 copy is at /swagger.json.
/openapi.jsonapi.md
MarkdownThe agent-readable reference: base URL, auth schemes, resources, field aliases, webhook events, and a sample call.
/api.mdapi/errors.json
JSONThe error catalog: stable codes, HTTP status, retryability, and resolution hints.
/api/errors.json.well-known/api-catalog
RFC 9727 linksetThe standard API catalog pointing at the spec and the service descriptor.
/.well-known/api-catalogFor AI Agents
The MCP server, the function-calling manifest, and the instructions an agent should read before it calls anything.
MCP server
HTMLShared API actions for contacts, messages, quotes, branded PDFs, underwriting, priorities, and links through Claude, ChatGPT, Grok, Grok Bots, Muse AI, dots, Gemini, and compatible developer tools.
/mcp-server.well-known/mcp.json
JSONThe MCP discovery document: transport, authentication, and capabilities. Mirrored at /.well-known/mcp.
/.well-known/mcp.json.well-known/mcp/server-card.json
JSONThe full server card: tools, scopes, resources, auth, and the error format.
/.well-known/mcp/server-card.json.well-known/tools.json
JSONSix ready-made OpenAI and Anthropic function definitions with typed JSON Schema parameters. Also at /ai-tools.json.
/.well-known/tools.json.well-known/agent-instructions.md
MarkdownWhat the service is, when to use it, when not to, and how to call the API.
/.well-known/agent-instructions.md.well-known/agent-skills
Agent Skills 0.2 discoveryA skills index pointing at the instructions, API docs, function-calling tools, and the Markdown twins.
/.well-known/agent-skills/index.json.well-known/ai-plugin.json
JSON, AI plugin manifestThe plugin manifest: capabilities, features, positioning, and discovery endpoints.
/.well-known/ai-plugin.jsonAuth Discovery
The OAuth and OpenID metadata clients need to authenticate without reading a doc.
.well-known/oauth-authorization-server
RFC 8414 JSONAuthorization server metadata for the OAuth 2.0 authorization code flow and its 20 scopes.
/.well-known/oauth-authorization-server.well-known/oauth-protected-resource
RFC 9728 JSONProtected resource metadata the MCP server and API point clients to.
/.well-known/oauth-protected-resource.well-known/openid-configuration
OpenID Connect JSONOpenID Connect discovery for sign-in based integrations.
/.well-known/openid-configurationFor LLMs and Answer Engines
The product, pricing, carrier, and positioning facts in the formats answer engines read first.
llms.txt
Markdown, text/plainThe AI discovery file: what unLocked is, carrier counts, pricing, modules, and positioning against the alternatives.
/llms.txtllm.txt
Markdown, text/plainCompact company facts: category, users, modules, founder, pricing, and a plain-language summary.
/llm.txtllms-full.txt
Markdown, text/plainThe long-form context document covering every product line, AI tool, integration, tier, and comparison.
/llms-full.txtai-data.json
JSON-LDMachine-readable company, products, pricing, modules, product lines, reviews, and discovery endpoints.
/ai-data.jsonCluster indexes
Markdown, text/plainTopic-scoped llms.txt files for the blog, comparisons, Medicare, and quoting clusters.
/blog-llms.txtFor Crawlers and Readers
Sitemaps, feeds, crawler directives, and Markdown twins of every page.
sitemap.xml
XML sitemap indexSix sub-sitemaps: pages, blog, comparisons, directories, international, and Markdown twins.
/sitemap.xmlrobots.txt
text/plainAllows Googlebot, Bingbot, and every major AI crawler, and advertises the sitemaps and feeds.
/robots.txtblog.xml
RSS 2.0The blog feed. The product updates feed is at /changelog.xml.
/blog.xmlMarkdown twins
XML sitemap of .md mirrorsEvery article and pillar page is mirrored as clean Markdown at its URL plus .md. This sitemap lists all of them.
/sitemap-markdown.xmlHow Crawlers and Agents Find These Files.
01
From the HTML head
Every page declares rel="ai-info" for llms.txt and llm.txt and rel="ai-data" for ai-data.json, so a crawler that lands anywhere finds the discovery files.
02
From robots.txt
Crawler directives allow GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and the rest by name, and advertise the sitemap index, the feeds, and the Markdown sitemap.
03
From the well-known paths
MCP, OAuth, OpenID, the API catalog, the tool manifest, the agent instructions, and the agent skills index all sit under /.well-known/ at their standard names.
04
From JSON-LD on every page
Organization, SoftwareApplication, FAQPage, and Article schema carry canonical sameAs links to the review directories and social profiles.
Developer Portal FAQ
What is the unLocked CRM developer portal?
The index of every machine-readable resource unLocked CRM publishes: the REST API and its OpenAPI 3.1 spec, the MCP server card and discovery document, the function-calling tool manifest, the agent instructions and skills index, OAuth and OpenID discovery, the llms.txt family and ai-data.json, and the sitemaps, feeds, and Markdown twins.
Where do I start if I am building an integration?
Read the API reference at /api, import /openapi.json into your client, create an API key in Settings under API, and subscribe to the webhook events you need through the webhooks resource. Errors come back as JSON with a stable code, catalogued at /api/errors.json.
Where do I start if I am connecting an AI assistant?
Point the client at mcp.unlockedcrm.ai and authorize with OAuth 2.0. The discovery document at /.well-known/mcp.json and the server card at /.well-known/mcp/server-card.json describe the transport, auth, and published tools. Read /api#supported-actions for the latest supported capability catalog. For plain function calling, /.well-known/tools.json has six ready-made definitions.
Which files should an LLM read to describe unLocked accurately?
Start with /llms.txt for the facts and positioning, /llms-full.txt for the complete context, and /ai-data.json for structured data. The agent instructions at /.well-known/agent-instructions.md say when to use and not use the service. Cluster indexes narrow the blog, comparison, Medicare, and quoting content.
Is every page available as Markdown?
Yes. Every article and pillar page has a Markdown twin at its URL plus .md, and the Markdown sitemap lists them all. The API reference itself is at /api.md.