Anvia Docs

Studio reports runtime capabilities from /config. The UI uses this shape to decide which surfaces should be available.

curl http://localhost:4021/config

{
  "id": "anvia-studio",
  "agents": [],
  "pipelines": [],
  "chat": {
    "quickPrompts": {}
  },
  "capabilities": {
    "agents": { "enabled": true },
    "sessions": { "enabled": true },
    "traces": { "enabled": true }
  },
  "unsupportedCapabilities": []
}

Capability List

Capability	Enabled when
`agents`	Always enabled
`sessions`	Session storage is available
`traces`	Trace storage is available
`tools`	At least one registered agent has static tools or dynamic tool indexes
`mcps`	At least one registered agent has tools registered from an MCP server
`pipelines`	At least one pipeline is registered
`observability`	At least one registered agent has observers
`approvals`	At least one registered agent has a tool with approval metadata or a runtime hook
`knowledge`	At least one registered agent has static context, dynamic context, or dynamic tools

Unsupported Capabilities

If a capability is unavailable, Studio lists it in unsupportedCapabilities. Requests to unsupported routes return an unsupported_capability error.

{
  "unsupportedCapabilities": ["sessions", "traces"]
}

Most applications should inspect /config before building custom tooling around optional Studio surfaces.