Analytics, artifacts, stages, and tables API
Query telemetry, export bounded results, retrieve immutable artifacts, inspect and recover stages, and read table state.
Analytics
| Method | Path | Purpose |
|---|---|---|
GET | /v1/namespaces/:namespace/analytics/summary | Read a bounded recent summary |
POST | /analytics/live | Read recent hot events and series |
POST | /analytics/dashboard | Read model, Agent, operation, cost, and time-series dashboard data |
POST | /analytics/query | Query aggregate or raw historical archive data |
POST | /analytics/exports | Materialize a bounded historical query as a content-addressed artifact |
GET | /analytics/exports/:ref | Download that namespace-owned export |
The last five relative paths begin /v1/namespaces/:namespace. See Query and export analytics for request limits.
Immutable artifacts and audit exports
| Method | Path | Purpose |
|---|---|---|
GET | /v1/artifacts/:ref | Read an authorized content-addressed platform artifact |
GET | /v1/exports/:ref | Read one redacted durable export delivered by the runtime |
GET | /v1/anchors/:ref | Read one authorized customer audit anchor |
Artifact references are hashes, not bearer authority; every read still evaluates Policy.
Data stages and tables
| Method | Path | Purpose |
|---|---|---|
GET | /v1/stages/:stageId | Inspect one map/reduce stage |
POST | /v1/stages/:stageId/recover | Request authorized stage recovery |
GET | /v1/namespaces/:namespace/tables/:table?branch=main | Read a table branch head and state |
GET | /v1/namespaces/:namespace/table-exports/:table/:branch/:seq/:hash | Read an exact catalog commit, export, or intent |
Agent code creates stages through registered ctx.map() and ctx.reduce() definitions. Operators use these routes for inspection and explicit recovery; they do not submit arbitrary stage code through the API. Runtime-only capability callbacks, sandbox egress, and internal /internal/v1 routes are not tenant Bearer APIs and are intentionally excluded from this user reference.
Agent-side historical exploration uses the SDK tableDescribe and tableQuery Tools rather than an HTTP SQL endpoint. Plans are structurally bounded and run against one authorized, exact snapshot. The platform injects the complete tenant and snapshot scope and keeps storage credentials behind the Resource boundary.