API delivery
Outcome API and feature feeds
Read-only delivery for scoped outcomes, provenance records, and evidence-linked state changes when your team needs CMD+RVL data inside an internal system.
Short answer
Use the Outcome API when a defined CMD+RVL result needs a reliable read path, not another exported spreadsheet or pasted prompt context.
What the API carries
The API is a delivery surface for a defined result. It does not turn every CMD+RVL system into a public endpoint.
Scoped outcome reads
Read the outcome state your engagement defines: monitored entity, current status, changed fields, timestamps, and stable identifiers.
Evidence-linked records
Return provenance references and evidence pack links with the delivery, so internal tools can point users back to the source trail.
Feature feeds
Move normalized change data into agent workflows, dashboards, or internal applications when a webhook alone is too thin.
Engagement-level guardrails
Endpoints, cadence, pagination, and access controls are planned around the package, monitor, or enterprise proof path.
Endpoint shapes
These examples show the shape of delivery discussions. Exact routes and payloads are scoped to the outcome.
GET /v1/outcomes/{outcome_id}
Read the current state and delivery metadata for one scoped outcome.
GET /v1/outcomes/{outcome_id}/evidence-pack
Fetch evidence pack references, source links, and provenance records for the latest state.
GET /v1/events?status=changed&limit=50
Pull recent state transitions for systems that need polling or replay.
Good fit when
- An internal application needs outcome state without manual exports.
- An agent needs stable identifiers and evidence links instead of pasted context.
- A dashboard or workflow needs a feature feed with provenance attached.
- Your team wants webhook delivery plus an API path for replay and reconciliation.
Plan the delivery before the endpoint
Start with the decision, system, cadence, and evidence record your team needs. The endpoint design follows from that scope.
What is the CMD+RVL Outcome API?
The CMD+RVL Outcome API is scoped API and feed delivery for outcomes, provenance records, evidence packs, and state transitions that are part of a package, operated monitor, or enterprise proof path.
Is this a standalone public API?
No. API delivery is planned inside a CMD+RVL engagement so endpoints, cadence, access controls, and evidence records match the outcome being operated.
What can agents do with the feeds?
Agents can read stable identifiers, current state, change events, and evidence links. That lets them act on bounded data without losing the source trail.
How is API delivery different from webhooks?
Webhooks push transitions as they happen. API delivery gives systems a read path for current state, evidence references, replay, reconciliation, and feature feeds.