Build with an AI agent

Agents help on two sides of the Partner API. A coding agent writes and debugs the integration, if it has the contract. Everything below hands it over, and none of it needs a key. Once companies are in Clemta, your team can ask an agent about them instead of opening a dashboard. That part is at the end of this page.

Skills

Two skills cover the Partner API. Each is a Markdown file an agent loads when the task matches its description, and each names the other.

Skill	Covers
`clemta-partner-quickstart`	Creating companies, ordering services, handling requirements, reading events. Includes the request rules: auth, idempotency, versioning, errors, and the sandbox.
`clemta-partner-webhooks`	Writing or debugging a webhook handler: tunnel, simulate, verify, reconcile by polling.

Install both:

npx skills add https://docs.clemta.com

Docs search

A search server for these docs runs at https://docs.clemta.com/mcp. Connect it and the agent looks things up here as it works. It searches the docs and does not call the API.

claude mcp add --transport http clemta-docs https://docs.clemta.com/mcp

{
  "mcpServers": {
    "clemta-docs": { "url": "https://docs.clemta.com/mcp" }
  }
}

{
  "servers": {
    "clemta-docs": { "type": "http", "url": "https://docs.clemta.com/mcp" }
  }
}

The Connect entries in the menu at the top of every page do the same in one click.

Markdown, llms.txt, and the spec

Add .md to any page URL for its Markdown: https://docs.clemta.com/partner/webhooks.md.
/llms.txt lists every page. /llms-full.txt is the whole site in one file.
The OpenAPI description is served from the API without a key: https://api.clemta.com/v1/openapi.json. See OpenAPI specs for the dated URLs.

Any of these can go in a CLAUDE.md, AGENTS.md, or .cursorrules file.

A starting prompt

With a skill or the docs server connected:

Integrate the Clemta Partner API. Use my clmt_test_ key from CLEMTA_API_KEY.
Create a company for a customer, expose a webhook handler that verifies
signatures, and move the test company to active with the sandbox so I can see
company.incorporated arrive.

When an agent holds a key

The key sets the mode. A clmt_test_ key never reaches live objects, and /sandbox/* refuses live keys. Give an agent a live key only when it should act on real companies.
Keep keys in an environment variable or the agent’s secret store. Never put one in a prompt, a skill file, or a committed file.
Send an Idempotency-Key on every write. An agent that retries a timed-out POST /companies without one forms two companies.
When a request fails with invalid_request, the errors array names every field. Pass that list to the agent. A blind retry fails the same way.

Not just for code

Once a company is in Clemta, your team can ask about it in plain words. An operations lead connects Claude, Cursor, or any MCP client to the Clemta MCP server with a Partner API key and asks: which companies are waiting on a document, what stage an order is at, when a filing is due. The answers come from the same objects your integration works with. The server is in development.

Where the skills come from

The skills are written from these guides and stay in step with them: Quickstart, How it fits together, Idempotency, Versioning, Errors, Webhooks, and Local development. For everything agent-related across Clemta, see AI agents.

Get Started

The platform

Building on the API

Versioning

Build with an AI agent

Skills

Docs search

Markdown, llms.txt, and the spec

A starting prompt

When an agent holds a key

Not just for code

Where the skills come from

​Skills

​Docs search

​Markdown, llms.txt, and the spec

​A starting prompt

​When an agent holds a key

​Not just for code

​Where the skills come from

Skills

Docs search

Markdown, llms.txt, and the spec

A starting prompt

When an agent holds a key

Not just for code

Where the skills come from