Skip to main content
GET
El catalogo: que secciones, objetivos y canales existen
The source of truth for every value you can put in section, goal.type and channels. Read it instead of hardcoding a list: a section added to the platform shows up here without this API publishing a version, and a list you copied into your code goes stale the day that happens. Each section row also carries a tip, which is the platform’s own guidance on what belongs in that section. If you generate section text with an LLM, that tip is the instruction to give it.

Endpoint

Required scope

agents:read

Query parameters

Example request

Response

200 OK

401 Unauthorized

Missing, invalid, revoked, or expired token.

403 Forbidden

The token does not have the agents:read scope.

502 Bad Gateway

The agent service is unreachable.

Operational notes

  • The catalogue is per company. A business can have its own wording for a section, and you get that wording, not the platform default.
  • toolkits only means something on goals. It names which tool families the goal switches on — that is why the goal is not just a label.
  • order is the order the sections take in the prompt, and it is also a sensible order to present them in a UI.
  • prompt is not exposed. Each row has one internally: it is the text that tells the agent what that section is. It is part of the system prompt, not integration surface.

Authorizations

Authorization
string
header
required

Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.

Query Parameters

kind
enum<string>

Familia del catalogo. Sin esto vuelven todas: secciones, objetivos y canales.

Available options:
section,
goal,
channel

Response

200 - application/json
data
object[]
required
total
number
required