Skip to main content
The product, the public Trust Center, and AI-agent integrations all talk to authenticated HTTP APIs. This page is what to hand an auditor who asked for “the API docs,” plus where the actual specification lives.

​
Surfaces

The product API has an OpenAPI specification: paths, request and response shapes, and which calls require authentication. That file is what an integration or a review should use, not this overview.

​
Access

  • Product and MCP APIs require authentication except for explicitly public endpoints (for example published Trust Center pages).
  • Tenant data is authorized from the signed-in user’s team and permissions, or from the credentials issued to the integrating client.

​
Using this for compliance

When someone asks for API documentation, send this, in this order:
  1. Share this page as the overview.
  2. Provide the API specification for the product API (available from your Keldyn workspace or account contact).
  3. For agent and IDE integrations, also share Keldyn MCP server.
  4. For public Trust Center surfaces, see your published Trust Center and Evidence & audits.