Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Contact channels

ChannelAddressUse for
Supportsupport@kindi.meIntegration help, API behavior questions, bug reports, account issues
Billingbilling@kindi.meToken balances, top-ups, receipts, quota questions
Securitysecurity@kindi.meVulnerability reports (see below)
Generalhello@kindi.meEverything else: partnerships, sales, press
Signed-in users also have an in-product help surface at dashboard.kindi.me/dashboard/support.

What to include in a report

The fastest reports contain, in rough order of usefulness:
  1. The request_id from the response body (or the request_id response header on errors). It pins the exact request server-side.
  2. Endpoint and timestamp (with timezone), e.g. POST /api/v1/mask at 2026-08-04 14:32 +03.
  3. HTTP status and response body you received.
  4. Your key prefix (the 8 characters after mk_live_), never the full bearer.
  5. A minimal reproduction: the smallest request that shows the problem. If the text itself is sensitive, a synthetic stand-in that still reproduces the behavior is ideal; use checksum-valid sample identifiers so detection behaves like production.
Never email real PII, decrypted mappings, or a full mk_live_ bearer. The key prefix plus request_id is enough to locate everything on our side.
Before reporting a detection issue, two quick checks that resolve most of them: is the missed type an extended entity that's toggled off? And does your test identifier pass its checksum? You can also reproduce any text case in the playground; if the playground succeeds where your code fails, the bug is client-side (the common mistakes guide covers the usual suspects).

Security issues

Email security@kindi.me with the subject line Security: <one-line summary>. We respond within 48 hours and aim to ship a fix, or document an accepted risk, within 7 business days. Please practice coordinated disclosure: give us the report before any public write-up, and don't test against other customers' data.

Service status

There is no public status page yet. The API's liveness probe is public and unauthenticated:
curl -s https://api.kindi.me/api/v1/health
(Remember it is reachable from Saudi IP addresses only.) The dashboard sidebar shows the same signal as a live status dot.