# The API covers everything in the interface

Every Krokul screen runs on the same API that is open to you: keys with role permissions, webhooks with retries, docs generated from the code, and MCP for AI agents.

**In short.** Krokul is a B2B CRM with a public API v1 that covers all the data and actions of the interface, because the interface itself runs on it. API keys are created with role permissions and a call log; webhooks send events (deal, document, payment, client company) with a delivery queue, retries and a log; the English documentation is generated from the code specification and includes examples from live responses; the MCP server lets AI agents read and act within the key’s permissions. All of this is part of the product, not a higher plan.

**Plan:** Available from the Money plan, $149 per month; MCP and higher limits on Margin

## What it looks like without Krokul

2. A webhook didn’t arrive because the client’s server was down for three minutes. The event is lost, the order isn’t created, and nobody notices.
3. The API is only on the expensive plan, and the documentation is three pages with no examples. The integration costs more than the CRM.

## What Krokul does

### One API for the screen and for you

The Krokul interface calls the same routes that an API key opens. A field you see on the screen is in the API too, by design, not by promise.

### Keys with role permissions

A key is created for a role: sales rep, accountant, read-only. Whatever the role can’t do, the key can’t either; every call is logged.

### Webhooks with a queue

Events about deals, documents, payments and client companies are sent to your URL with a queue, retries on failure and a delivery log. Undelivered events are visible and can be resent manually.

### Docs from code, and MCP

The specification is derived from the code and the examples from live responses, so the documentation doesn’t go stale. The MCP server connects AI agents with the same permissions as the key.

## How it works

1. **Create a key for a role** In settings: name, role, expiry. The key sees exactly what a person with that role would see.
2. **Read the documentation with examples** English documentation describing every route and its fields, with response examples, at the address linked in the site footer.
3. **Connect webhooks** A URL and events; the delivery log shows every attempt with its response code. On failure, it retries on schedule or manually.
4. **Connect an agent through MCP** A key and the MCP address, and an external AI agent reads data and proposes actions within its permissions, with the same log.

## Result

- No event is lost: the queue and retries deliver the webhook, and the log shows every attempt.
- The API, webhooks and MCP aren’t priced separately: they are part of the product.

## What’s not included

## Questions

### Does the API really cover everything?

Yes, because the interface runs on the same routes: we have no separate “internal” API with more capabilities.

### How do I limit what a key can see?

By role. A read-only key can’t create anything; a key with the sales rep role won’t see cost. The server enforces this.

### What if a webhook doesn’t arrive?

The delivery log shows the attempt and the response code; the retry happens automatically on schedule or manually with a button.

### What is MCP and why do I need it?

A protocol AI agents use to read data and call actions. Krokul has its own MCP server: connect an agent with a key, and it will see exactly what the role allows.

### How much does the API cost?

The API, keys and webhooks are included in the Money plan, $149 per month; MCP and higher call limits are on the Margin plan. Records created through the API count as transactions just like those created on screen.

### How do I connect a service that isn’t in the Marketplace?

With a custom integration rule: Kro drafts it from your description, the rule is test-run on sample events and can only be switched on after that run. The service sends an event to the rule’s address — Krokul finds the deal, document or contact and creates a payment, contact or task; every event stays in the log. Custom rules are on the Margin plan.

## Open the docs and make your first request

Create a key in settings, call the “client companies” route and get your list, in five minutes, without emailing support.

Included in the Money plan.

## Next in the chain

- [Automations: the system does the routine and shows why](https://krokul.com/en/solutions/automations/index.md)
- [The role decides who sees what. The server enforces it](https://krokul.com/en/solutions/security/index.md)
- [Your data is yours: API, export and rollback from day one](https://krokul.com/en/solutions/data/index.md)
- [An AI assistant that sets up the system in plain words](https://krokul.com/en/solutions/assistant/index.md)

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs