Analytics, artifacts, stages, and tables API

Query telemetry, export bounded results, retrieve immutable artifacts, inspect and recover stages, and read table state.

Analytics

MethodPathPurpose
GET/v1/namespaces/:namespace/analytics/summaryRead a bounded recent summary
POST/analytics/liveRead recent hot events and series
POST/analytics/dashboardRead model, Agent, operation, cost, and time-series dashboard data
POST/analytics/queryQuery aggregate or raw historical archive data
POST/analytics/exportsMaterialize a bounded historical query as a content-addressed artifact
GET/analytics/exports/:refDownload 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

MethodPathPurpose
GET/v1/artifacts/:refRead an authorized content-addressed platform artifact
GET/v1/exports/:refRead one redacted durable export delivered by the runtime
GET/v1/anchors/:refRead one authorized customer audit anchor

Artifact references are hashes, not bearer authority; every read still evaluates Policy.

Data stages and tables

MethodPathPurpose
GET/v1/stages/:stageIdInspect one map/reduce stage
POST/v1/stages/:stageId/recoverRequest authorized stage recovery
GET/v1/namespaces/:namespace/tables/:table?branch=mainRead a table branch head and state
GET/v1/namespaces/:namespace/table-exports/:table/:branch/:seq/:hashRead 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.