View your simulation data
Runtime telemetry ingestion
Runtime services use project tokens to create environments and publish operational data. The GUI reads this data back into telemetry, infrastructure, grid and causality views.
Supported ingestion routes
- Create environmentPOST /api/{org}/{project}/env/create
- System logsPOST /api/{org}/{project}/{env}/{instance}/system-log/ingest
- Infrastructure snapshotPOST /api/{org}/{project}/{env}/{instance}/infrastructure/full
- Event edges (~Spans)POST /api/{org}/{project}/{env}/{instance}/edge/ingest
Authentication
Bearer project token
Every runtime API route rejects missing tokens and checks project access before writing data.
Telemetry example
Publish system logs
System log batches appear in the environment telemetry page after they are ingested.
POST /api/{org}/{project}/ci/1/system-log/ingest
Authorization: Bearer {project-token}
{
"logs": [
{
"serviceType": "matchmaker",
"serviceId": "00000000-0000-0000-0000-000000000001",
"level": "Debug",
"message": "tick complete",
"timestamp": "2026-07-03T00:00:00Z"
}
]
}