RFQ and voice

RFQ and voice are negotiated execution paths for an instrument already defined by the catalogue. They do not change the model, provider, bundle, unit, or term being quoted.

Requests for quote

An RFQ names an instrument, side, size, expiry, and optional initiator limit. Public reads expose active RFQs and their detail. Creating an RFQ, submitting a quote, and accepting a quote act for the selected desk and require active account authority plus open venue, desk, and instrument controls.

Route	Purpose
GET /api/v1/rfqs	List RFQs
POST /api/v1/rfqs	Create an RFQ
GET /api/v1/rfqs/{id}	Read RFQ detail and quotes
POST /api/v1/rfqs/{id}/quotes	Submit a quote
POST /api/v1/quotes/{id}/accept	Accept a quote

A quote records its revision and source, such as SCREEN, VOICE, ALGO, or API. Treat route responses as the contract for resulting order and trade identifiers.

Voice sessions

A voice session records its participants, state, transcript segments, and proposed terms. The current session routes support creation, detail, transcript append, media signalling, confirmation, and end actions.

Proposed price and MFT values use exact decimal strings. Proposed spot size uses a whole-token integer. A client should submit the size representation appropriate for the instrument.

Confirmation and autonomy

Human confirmation is the default. With no stored policy, the desk operates in HUMAN_CONFIRM mode. A person restates and confirms the proposed terms with POST /api/v1/voice/sessions/{id}/confirm.

A desk can explicitly select AUTONOMOUS mode with PUT /api/v1/voice/autonomy when its account authority and venue controls are active. Autonomous mode requires declared limits for per-booking notional, rolling notional, rolling window, size, side-specific price, and optionally counterparties. A booking outside any declared limit is refused instead of adjusted. Switching back to HUMAN_CONFIRM remains available while controls block new exposure.

See Voice autonomy for the policy body and response fields.