Developers

Kairon for developers

Four doors, one product: an MCP server for a model, a CLI for a script, a REST API for a system, and the documents an agent reads before touching any of them.

The MCP server

The door for a model. Endpoint: https://app.heykairon.com/mcp (Streamable HTTP, JSON-RPC over POST). Every tool, with its arguments and an example, is on the MCP page; the same catalogue as JSON is at mcp-tools.json, and the server card a directory reads is at https://app.heykairon.com/.well-known/mcp/server-card.json. The server is listed in the official MCP registry as com.heykairon/kairon, and on Smithery.

Authentication

OAuth 2.1 with PKCE and dynamic client registration; every token is authorized by a person. The flow, step by step and with every URL, is in auth.md. Metadata: https://app.heykairon.com/.well-known/oauth-authorization-server and https://app.heykairon.com/.well-known/oauth-protected-resource.

The CLI

The door for a script. npx @kairon/cli login, then kairon <tool group> <command>: the same calls a model makes, from a terminal. Every command is on the CLI page; its commands are derived from the MCP catalogue, so the two cannot drift.

The REST API

The door for a system, behind an API key. OpenAPI at https://app.heykairon.com/docs-json (also /openapi.json), browsable at https://app.heykairon.com/docs, listed in api-catalog (RFC 9727). Pipeline changes can also reach you as signed webhooks: how to receive them.

What an agent reads first

  • llms.txt: when to use Kairon, how to call it, and every page in markdown.
  • ard.json: the Agentic Resource Discovery entry.
  • Markdown twins of the pages: the home, pricing, the FAQ, the webhooks guide, and /blog/<slug>.md for every post. Each of these pages also answers a request that prefers text/markdown with its twin.

Getting an account

Signing up at https://app.heykairon.com requests a 7-day trial; accounts are let in from a waitlist, so an agent cannot create one on its own. Questions go to the address on Contact.