Skip to content

REST API

The active controller tree verifies these groups:

  • /api/about
  • /api/auth/config
  • /api/agents
  • /api/providers
  • /api/users
  • /api/groups
  • /api/channels
  • /api/channels/conversations
  • /api/cli-tools
  • /api/mcp-servers
  • /api/remote-agents
  • /api/tools
  • /api/tasks
  • /api/metrics
  • /api/export* and /api/import*
  • /api/sessions and related session subroutes

Current session execution is async-first:

  • POST /api/sessions/execute
  • POST /api/sessions/execute-with-content

Live execution output is streamed back through SignalR.

When reading the repository’s older REST markdown, keep these corrections in mind:

  • the proposed synchronous execute endpoints are not implemented in the current controller tree
  • POST /api/sessions/execute does not return an empty body in current code
  • older portal README content describing public endpoints and direct hub invocation is stale

The hosted runtime also includes:

  • execution hub routes under the portal base path
  • async-operation hub routes under the portal base path
  • health endpoints
  • A2A discovery and messaging endpoints