Primust
Workspace
Integrations / Capture

Evidence capture sources

Gateway channels are shown only after model-call observations are recorded for the workspace.

Observed calls
0
Providers
0
Failed calls
0
Capture sources
0
Runtime Agent capture via SDK / API / Proxy

Use runtime capture when the agent is a production workflow or serving boundary rather than a local Mission Control hook.

Capture inventory appears after detectors, upstream sources, or gateway observations are returned by the API.
Gateway command
Not observedNot observed0 tokens
primust gateway serve --mode observe --port 8787
Detector wiring stays visible below so model-call capture, upstream sources, and Evidence sources can be checked from one page.
Gateway observations
Avg latency
Not observed
Tokens
0
Last observed
Not observed
Supported routes
0
ProviderStatusCallsModelsObserved routesAvg latencyTokensLast observed
No gateway model-call observations returned for this workspace.
Recent gateway records
ProviderModelRouteHTTP / resultLatencyTokensRecordedRun
No recent gateway records returned by the API.
Supported provider routes
ProviderSupported routes
Provider route metadata is unavailable.
Capture inventory

Upstream sources, Evidence sources, Detectors, and Detector wiring are folded into the core capture inventory so discovery stays connected to the agent and runtime flows.

Capture sourceTypeStatusLast seenAction
No results