Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runtools.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Runtools records customer-visible activity for important resource events: sandbox lifecycle, agent runs, thread messages, tool calls, workspace operations, installable-agent installs, code execution, and RunMesh device changes. This feed is for product observability and auditability. It is separate from internal service logs and metrics used by the Runtools team.

​
Activity Model

Each event has a resource, an actor, a status, a severity, timestamps, and optional attributes.
FieldMeaning
resourceTypesandbox, agent, workspace, thread, tool, installable_agent_install, runmesh_device, or code_execution
resourceIdResource identifier
eventTypeMachine-readable event name such as agent.run.started
severityinfo, warning, or error
statusEvent-specific state such as started, completed, failed, or added
actorUserIdUser who caused the event when known

​
Access Rules

Members see their own activity by default. Resource-scoped requests can return events for a resource the caller is allowed to access. Organization admins can filter across actors inside the organization.

​
Common Filters

cURL
curl "https://api.runtools.ai/v1/activity?resource_type=sandbox&resource_id=sandbox-abc123&limit=50" \
  -H "X-API-Key: $RUNTOOLS_API_KEY"
cURL
curl "https://api.runtools.ai/v1/threads/thr_abc123/activity" \
  -H "X-API-Key: $RUNTOOLS_API_KEY"
Use since and until for time windows, and cursor for pagination.

​
What Activity Is Not

Activity events are not the canonical thread transcript. Thread content lives in the thread event APIs. Transient token, reasoning, and tool-output deltas are live-only and are not activity rows.

Activity API

Query the org activity feed and resource-scoped activity endpoints.