Obtener un agente
GET /v1/agents/{id}
Get one agent whole: goal, prompt sections with their text, channels, tools and knowledge nodes.
GET
Obtener un agente
Returns one agent with everything the list endpoint leaves out: its goal, the sections of its prompt with their text, the channels it answers on, the tools it may call and the knowledge nodes it can search.
One call is enough. In the block model this replaced, the text lived somewhere else and reading a prompt took three calls; a section belongs to its agent, so it comes back here.
Endpoint
Required scope
agents:read
Headers
Path parameters
Example request
Response
200 OK
401 Unauthorized
Missing, invalid, revoked, or expired token.403 Forbidden
The token does not have theagents:read scope.
404 Not Found
No agent with that id in the token’s company and project.502 Bad Gateway
The agent service is unreachable.Operational notes
promptscarries the text. What each section is for comes from the catalogue; the order is the order they take in the assembled prompt.- A section that was never written is absent, not empty. There is no placeholder row per section type.
goal.typedecides which tools the agent can actually use, beyond the ids intools. Changing it changes the agent’s capabilities, not just a label.toolsandknowledge_node_idsare ids into company-level collections. Deleting the agent leaves them alone.- This endpoint returns inactive agents too, unlike the list.
is_active: falsemeans the agent does not answer, but its configuration is intact. - 404 covers the cross-project case. An agent that belongs to another project of the same company reads as not found, not as forbidden — the project of the token is part of its identity.
company,project,metadataandcreated_byare never returned. The first two are implied by the token, the third has no published schema, and the fourth is an internal user id.