VEX Consensus API (Contract Overview)

Audience: integrators consuming Stella Ops VEX consensus over HTTP.

This document provides a high-level overview of the consensus endpoints. The gateway and the VEX Lens architecture dossier define the authoritative routing, auth, and schema details; the shapes below are a quick reference, not the contract.

Common Headers

• Authorization: Bearer <token> (or DPoP where configured)
• X-StellaOps-TenantId: <tenantId> (required)

Typical Endpoints

• GET /v1/vex/consensus?artifact=...&advisory=... — returns a single consensus record (plus conflicts).
• GET /v1/vex/conflicts — list outstanding conflicts with summary metadata.
• GET /v1/vex/consensus/export — deterministic JSONL export for Offline Kit / Export Center bundles.
• POST /v1/vex/trust/weights — tenant-admin update of trust tiers/weights (when enabled).

Output Shape

See the Consensus JSON payload reference for the record payload reference.

References

• VEX Lens architecture
• Consensus algorithm (deterministic)
• Consensus JSON payload reference