For developers – Legamik

From complaint to cited letter in one integration.

Authenticate with a per-organization API key. Full machine-readable contract: OpenAPI specification.

Official TypeScript SDK (@legamik/sdk) is available to API partners.

POST/api/v1/complaintsCreate a complaint case from a plain-language description; letter generation runs asynchronously

GET/api/v1/complaints/{id}Case status and, once generated, the letter result

GET/api/v1/complaints/{id}/sourcesThe legal sources the letter stands on — full citation audit bundle

POST/api/v1/analyzeStructured analysis of a legal situation, without generating a letter

GET/api/v1/creditsPre-paid credit balance and the recent ledger entries

POST/api/v1/credits/topupStart a Stripe Checkout top-up of pre-paid credits

GET/api/v1/categoriesAvailable dispute categories

GET/api/v1/jurisdictionsAvailable jurisdictions

POST/api/v1/webhooksRegister a webhook endpoint

GET/api/v1/webhooksList registered webhook endpoints

PATCH/api/v1/webhooks/{id}Update a webhook endpoint

DELETE/api/v1/webhooks/{id}Revoke (soft-delete) a webhook endpoint

GET/api/v1/webhooks/deliveriesList webhook delivery attempts

HOOKcomplaint.completedFired when letter generation finishes successfully

HOOKcomplaint.failedFired when letter generation fails

Quickstart · curl

curl https://api.legamik.com/api/v1/complaints \
  -H "Authorization: Bearer <your API key>" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Roční vyúčtování záloh neodpovídá
      uzavřené smlouvě ani skutečné spotřebě
      podle samoodečtu z 31. 3. 2026.",
    "entity": "ČEZ Prodej, a. s.",
    "category": "utility",
    "jurisdiction": "CZ"
  }'

HTTP/1.1 201 Created
{ "complaint": {
    "id": "…",
    "status": "processing",
    "createdAt": "2026-06-13T09:00:00.000Z" } }

Agents prepare. Humans decide.

An MCP server exposes the dispute flow as agent tools — open a case, fetch the cited letter, list categories and jurisdictions, manage credits. One rule is enforced server-side: no letter is ever sent without explicit end-user confirmation. Case data is never used to train AI models; all processing is governed by the privacy policy.

Available for B2B partners — POST /mcp (Streamable HTTP) with the same API key as the REST API. The server speaks the current MCP revision, 2026-07-28.

generate_complaintOpen a case from a plain-language description; the cited letter generates asynchronously

get_complaintPoll case status and fetch the finished letter

list_categoriesLive dispute categories

list_jurisdictionsSupported jurisdictions (CZ active)

get_credit_balanceCurrent pre-paid credit balance

create_topupCreate a Stripe checkout to top up credits — a human completes the payment

Connect · MCP client config

{
  "mcpServers": {
    "legamik": {
      "type": "http",
      "url": "https://api.legamik.com/mcp",
      "headers": {
        "Authorization": "Bearer <your API key>"
      }
    }
  }
}

Pricing & credits

Same prices as the consumer web — B2C parity, no partner markup. Billing is pre-paid: your organization holds a CZK credit balance and each successful call consumes its listed price.

Cited complaint lettergenerate_complaint · POST /api/v1/complaints249 Kč

Legal-situation analysisPOST /api/v1/analyze99 Kč

Top up with the create_topup tool or the REST equivalent: 1–50,000 CZK per checkout; a human completes the returned Stripe checkout URL and credits settle within seconds.
Failed generations are refunded to the balance automatically; idempotent retries (same idempotency key) are never charged twice.

Build on Legamik.

From complaint to cited letter in one integration.

Agents prepare. Humans decide.

Pricing & credits

Get API access