Documentation Index
Fetch the complete documentation index at: https://mintlify.com/everruns/everruns/llms.txt
Use this file to discover all available pages before exploring further.
GET /v1/capabilities
List all available capabilities that can be enabled on agents. Capabilities provide tools, system prompt additions, and behavior modifications.Response
Array of capability objects
Capability identifier. Format:
- Built-in:
snake_case(e.g.,current_time,web_fetch) - MCP:
mcp:{server_uuid}(e.g.,mcp:01933b5a-0000-7000-8000-000000000501)
Display name
Description of functionality (supports GitHub Flavored Markdown)
Availability status:
available, experimental, deprecatedIcon name for UI rendering
Category for grouping in UI (e.g., “Utilities”, “Data”, “MCP Servers”)
true if this is an MCP virtual capabilityIDs of capabilities this capability depends on
UI feature strings this capability contributes to (e.g.,
file_system, secrets)Risk classification:
low (default, omitted), medium, highTotal number of capabilities
Example Request
Example Response
Capability Types
Built-in Capabilities
Built-in capabilities are defined in the Everruns codebase and usesnake_case identifiers:
current_time- Get current date and timeweb_fetch- Fetch content from URLssession_file_system- File operations in session workspacevirtual_bash- Sandboxed bash shellsession_storage- Key/value and secret storagestateless_todo_list- Task trackingsample_data- Sample data filesskills- Skills discovery from session VFSplatform_management- Manage harnesses, agents, sessions
MCP Virtual Capabilities
MCP servers are exposed as “virtual capabilities” with IDs in the formatmcp:{server_uuid}. They appear alongside built-in capabilities in the UI but:
- Tools are prefixed with
mcp_{server_name}__ - Availability depends on server status
- No system prompt additions or dependencies
- Display an “MCP” badge in the UI
Capability Dependencies
Capabilities can depend on other capabilities. When a capability is selected:- Dependencies are automatically resolved and applied
- Dependencies are always applied before dependents (topological order)
- Only user-selected capabilities are stored; dependencies are resolved at runtime
- Users cannot remove a capability required by other selected capabilities
virtual_bash depends on session_file_system. Selecting virtual_bash automatically enables session_file_system.
Capability Features
Capabilities declare UI features they contribute to. The UI uses these to determine which tabs/sections to render:| Feature | UI Element |
|---|---|
file_system | Workspace tab |
secrets | Storage tab |
key_value | Storage tab |
schedules | Schedules tab |
sql_database | (reserved) |
Risk Levels
Capabilities are classified by risk level:| Level | Description | Admin Required |
|---|---|---|
low | Default. No special requirements. | No |
medium | Logged but allowed for org members. | No |
high | Can execute arbitrary code or access external resources. | Yes |
virtual_bash, web_fetch, docker_container, daytona, codesandbox
Using Capabilities
Create Agent with Capabilities
Update Agent Capabilities
Session-Level Capabilities
Capabilities can also be set at the session level, extending the agent’s capabilities:Error Responses
Error message
HTTP status code
Common Errors
- 500 Internal Server Error: Server error during capability retrieval