Clidelity Developer Documentation

Clidelity builds sales systems for women coaches and consultants. For agents and developers, the primary surface is a read-only MCP server behind OAuth. The public HTTP endpoints exist for the product's own pages and are documented for completeness. Every machine-readable resource lives at a predictable URL below.

• Agent integration guide

  Start here. The MCP endpoint, the OAuth discovery chain, the three read-only tools, auth, and how account access works.

• OpenAPI specification

  The public HTTP endpoints behind the intake, screening, and testimonial pages. Typed schemas, operation ids, the JSON error shape every endpoint uses, and the versioning, deprecation, and rate limit header conventions.

• MCP server manifest

  The Model Context Protocol server at /mcp in one machine-readable card. Streamable HTTP transport, OAuth bearer auth, three read-only tools.

• OAuth protected resource metadata

  RFC 9728. Names the authorization server Clidelity trusts and the supported scopes.

• OAuth authorization server metadata

  RFC 8414. The authorization, token, and registration endpoints, relayed from the server that owns them.

• llms.txt

  The index of everything on this page in the llmstxt.org format, with when-to-use guidance for agents.

Access requires a Clidelity coach account. The fourteen day trial and the tester seats are on the pricing page. Questions and integration requests reach a person at hello@khudco.com, or through the contact page.