Debugging
Inspect and debug running Rivet Actors using the management and actor inspector HTTP APIs.
Management API
The management API runs on the root path and is used to list, create, and look up actors.
Authentication
| Environment | Authentication |
|---|---|
| Local development | No authentication required. All endpoints are accessible without tokens. |
| Self-hosted engine | The Rivet Engine handles authentication. Set RIVET_TOKEN to enable authenticated access to restricted endpoints like KV. |
| Rivet Cloud | Authentication is handled by the Rivet Cloud platform. Use your project token passed via the x-rivet-token header. |
Restricted endpoints (like KV reads) require the x-rivet-token header:
List Actors
Returns:
Create or Get Actor
Returns the actor object with its actor_id.
List Actor Names
Returns all registered actor names and their metadata.
Read Actor KV
Requires authentication (see above).
Returns the value stored at the given key.
See the OpenAPI spec for the full schema of all management endpoints.
Actor API
All actor-level endpoints are accessed through the gateway. The gateway routes requests to the correct actor instance using the actor ID in the URL path:
The gateway only accepts actor IDs, not names. Use GET /actors?name=... from the management API to look up actor IDs first.
Authentication
Standard actor endpoints (health, actions, requests) and inspector endpoints have separate authentication requirements.
Standard Endpoints
| Environment | Authentication |
|---|---|
| Local development | No authentication required. |
| Self-hosted engine | The Rivet Engine handles authentication at the gateway level. |
| Rivet Cloud | Authentication is handled by the Rivet Cloud platform at the gateway level. |
Inspector Endpoints
| Environment | Authentication |
|---|---|
| Local development | No authentication required if RIVET_INSPECTOR_TOKEN is not set. A warning is logged. |
| Self-hosted engine | Set the RIVET_INSPECTOR_TOKEN environment variable. Pass it as a bearer token in the Authorization header. |
| Rivet Cloud | Token is required. Pass it as a bearer token in the Authorization header. |
Standard Actor Endpoints
These are the built-in actor endpoints available through the gateway:
Inspector Endpoints
The inspector HTTP API exposes JSON endpoints for querying and modifying actor internals at runtime. These are designed for agent-based debugging and tooling.
Get State
Returns the actor’s current persisted state:
Set State
Returns:
Get Connections
Returns all active connections with their params, state, and metadata:
Get RPCs
Returns a list of available actions:
Execute Action
Returns:
Get Queue Status
Returns queue status with messages:
Get Traces
Query trace spans in OTLP JSON format:
Returns:
Get Workflow History
Returns:
Summary
Get a full snapshot of the actor in a single request:
Returns:
Polling
Inspector endpoints are safe to poll. For live monitoring, poll at 1-5 second intervals. The /inspector/summary endpoint is useful for periodic snapshots since it returns all data in a single request.
OpenAPI Spec
The full OpenAPI specification including all management and actor endpoints is available:
- In the repository at
rivetkit-openapi/openapi.json - Served at
/docon the manager when running locally