Skip to main content
GET
List agents visible to you

Authorizations

Authorization
string
header
required

Session JWT. After nasiko auth login, print it with jq -r '.clusters[.active].token' ~/.nasiko/config.json. API keys aren't supported.

Query Parameters

owner
string<uuid> | null
status
string | null
limit
integer<int64>
offset
integer<int64>

Response

200 - application/json

Agents visible to the caller

capabilities
any
required
created_at
string<date-time>
required
default_input_modes
string[]
required
default_output_modes
string[]
required
id
string<uuid>
required
metadata
any
required
minimal_code_enabled
boolean
required

Whether minimal-code guidance is injected into messages sent to this agent. Shown as a switch on the agent's Settings tab.

name
string
required
owner_id
string<uuid>
required
preferred_transport
string
required
protocol_version
string
required
security_schemes
any
required
skills
object[]
required
status
string
required
tags
string[]
required
updated_at
string<date-time>
required
version
string
required
compress_enabled
boolean

Per-agent opt-in for compression on this agent's traffic: payload compression on its LLM calls, brevity, and session-history compression in direct chats. Off unless enabled.

description
string | null
display_name
string | null
documentation_url
string | null
hitl_enabled
boolean

Whether this coding agent gates its tool use behind human approval. Off unless explicitly enabled; only meaningful for workload_kind = acp_coding_agent.

icon_url
string | null
image
string | null
transport_path
string | null

Path of the agent's advertised JSON-RPC transport (e.g. "/jsonrpc"), extracted from its AgentCard supportedInterfaces at deploy time. Clients chat via {base}/api/agents/{id}{transport_path}.

url
string | null
workload_kind
string

Workload kind: agent (default), mcp_connector, or acp_coding_agent. Exposed so clients can tell a coding agent apart from a normal one (e.g. nasiko chat labels it, and --coding-agent asserts on it).