Kontent.ai
for LuumenAI

Read Kontent.ai content items, types, and languages from the terminal

Ask what a content item actually contains before you debug a broken page. Luumen reads Kontent.ai over an API key: KONTENT_AI_LIST_CONTENT_ITEMS and KONTENT_AI_GET_CONTENT_ITEM for the content itself, KONTENT_AI_GET_LANGUAGE_VARIANT for a specific locale, and KONTENT_AI_LIST_CONTENT_TYPES with KONTENT_AI_GET_TYPES_ELEMENT for the model behind it. Read-only, answered in place.

The Kontent.ai toolbox

7 tools, all read-only. They answer instantly, and every call is logged.

  • ReadGet Content ItemRetrieve a specific content item by its identifier.
  • ReadGet LanguageRetrieve a specific language by its ID.
  • ReadGet Language VariantRetrieve a specific language variant of a content item.
  • ReadGet Content Type ElementRetrieve a specific element from a content type by codename.
  • ReadList Content ItemsList content items from the Delivery API.
  • ReadList Content TypesList content types within a Kontent.ai environment.
  • ReadList LanguagesList languages in a Kontent.ai project.

Questions

How does LuumenAI connect to Kontent.ai?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Kontent.ai on its own?

No. Every one of the 7 tools LuumenAI has for Kontent.ai is read-only, so it can answer questions from Kontent.ai but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.

Who gets access to the integration?

You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.

Is there an audit trail?

Every call to Kontent.ai is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Kontent.ai to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.