HTTP API

Endpoints

Call Studio routes from scripts, tests, or custom internal tools.

Studio exposes the same runtime used by the bundled UI as an HTTP API.

Core Endpoints

EndpointMethodPurpose
/healthGETCheck that the runtime is alive
/configGETRead agents, quick prompts, and enabled capabilities
/agentsGETList registered agents
/agents/:agentIdGETRead one agent config
/agents/:agentId/toolsGETInspect registered tool metadata for one agent
/agents/:agentId/mcpsGETInspect registered MCP server and tool metadata for one agent
/agents/:agentId/runsPOSTRun an agent
/pipelinesGETList registered pipelines
/pipelines/:pipelineIdGETRead pipeline metadata and graph
/pipelines/:pipelineId/runsPOSTRun a pipeline with JSON input
/pipelines/:pipelineId/logsGETRead metadata-only pipeline audit logs
/sessionsGET, POSTList or create sessions
/sessions/:sessionIdGET, DELETERead or delete a session
/sessions/:sessionId/logsGETRead metadata-only session audit logs
/sessions/:sessionId/tracesGETList traces for a session
/tracesGETList traces
/traces/:traceIdGETRead one trace
/approvalsGETList pending or resolved approvals
/approvals/:approvalId/decisionPOSTApprove or reject a tool call
/questionsGETList pending or answered human question requests
/questions/:questionId/answerPOSTAnswer an ask_question tool request
/knowledgeGETInspect agent context, dynamic retrieval sources, and recent trace evidence

Error Shape

{
  "error": {
    "code": "bad_request",
    "message": "Request body must be JSON"
  }
}

Error codes are bad_request, conflict, not_found, unsupported_capability, and internal_error.

For request examples, see Run Requests, Streaming Runs, Tool Approvals, and Human Questions.