One place to find every agent and API contract.
Use the human-readable guides for integration decisions and the machine-readable files for discovery, typed calls, authentication, and recovery.
REST API and agent documentation.
The control API provisions and manages a project; the edge API uses provisioned services. Start with the installer rather than calling tenant creation by hand, keep project credentials server-side, and read the selected offering page before making edge calls.
- Documentation index
Start here for onboarding, lifecycle, pricing, and links to every machine-readable surface.
GET https://cohesivity.ai/docs - OpenAPI 3.1 description
Typed discovery for bootstrap and common control-plane operations, including errors and response headers.
GET https://cohesivity.ai/openapi.json - Authentication guide
Tenant keys, wait tokens, public MCP access with optional account OAuth, PKCE, and credential boundaries.
GET https://cohesivity.ai/auth.md - Agent instructions
When to use cohesivity, how an agent should set up a project, and where each offering contract lives.
GET https://cohesivity.ai/llms.txt - Offering references
Endpoints, prerequisites, tier behavior, current limits, and common mistakes for every public service.
GET https://cohesivity.ai/offerings
Model Context Protocol.
The anonymous documentation server and OAuth-protected management server are separate on purpose. The first retrieves public references. The second exposes a fixed allowlist of account and tenant tools, rechecks ownership on every tenant call, and does not return tenant keys, provider secrets, environment values, or raw wait capabilities.
- MCP discovery metadata
Use cohesivity’s vendor-defined alias to discover the one public server for documentation and management, its optional account OAuth, and its Streamable HTTP transport.
GET https://cohesivity.ai/.well-known/mcp.jsonPOST https://cohesivity.ai/mcp - MCP OAuth protected resource metadata
Discover the authorization server for optional account sign-in on the same MCP server.
GET https://cohesivity.ai/.well-known/oauth-protected-resource/mcp
Versioning and recovery.
REST responses identify the current API major version, tenant status identifies the pinned runtime profile, and deprecations use published response headers plus a migration document. If a public page URL does not exist, its 404 points agents back to the sitemap, llms.txt, docs index, and this developer index. Unknown API routes keep the structured JSON error contract.