# Kontent.ai AI integration on Definable

> Kontent.ai is a headless CMS that delivers content via API, allowing developers to build websites and applications using their preferred frameworks, languages, or libraries.

## What this connects

Kontent.ai is a headless CMS that delivers content via API, allowing developers to build websites and applications using their preferred frameworks, languages, or libraries.

Vendor: https://kontent.ai

## Tools available

**7** tools available. First 7:

- `KONTENT_AI_GET_CONTENT_ITEM` — Get Content Item — Tool to retrieve a specific content item by its identifier. Use after confirming the environment ID and item identifier.
- `KONTENT_AI_GET_LANGUAGE` — Get Language — Tool to retrieve a specific language by its ID. Supports Management API directly and Delivery API via normalization.
- `KONTENT_AI_GET_LANGUAGE_VARIANT` — Get Language Variant — Tool to retrieve a specific language variant of a content item. Use after confirming the item and language identifiers when needing localized content.
- `KONTENT_AI_GET_TYPES_ELEMENT` — Get Content Type Element — Tool to retrieve a specific element from a content type by codename. Use when you need to get details about an element's configuration within a content type.
- `KONTENT_AI_LIST_CONTENT_ITEMS` — List Content Items — Tool to list content items from the Delivery API. Use when fetching content items for a specified environment, optionally providing a continuation token for pagination.
- `KONTENT_AI_LIST_CONTENT_TYPES` — List Content Types — Tool to list content types within a Kontent.ai environment. Use when you need to retrieve a paginated list of content type definitions. Use after confirming the environment ID.
- `KONTENT_AI_LIST_LANGUAGES` — List Languages — Tool to list languages in a Kontent.ai project. Use when you need to retrieve all languages for a specified environment after confirming the project ID.

## Auth

Auth schemes: `API_KEY`.

## How agents use Kontent.ai

Inside a Definable workflow, Kontent.ai is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Kontent.ai** — the Researcher (GPT-5.5) pulls context from Kontent.ai (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Kontent.ai** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Kontent.ai (create record, post message, draft email).
- **Designer / Engineer → Distributor → Kontent.ai** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Kontent.ai (attach file, open PR comment, post status).

The Verifier checks every Kontent.ai call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- documents — https://definable.ai/apps/category/documents/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/kontent_ai/
- Same category (documents): https://definable.ai/apps/category/documents/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt