The API is intentionally upstream of execution. It produces IBKR contract drafts and order templates, while Vertex Quant on QuantVPS owns the live runtime, broker connection, risk layer, and kill switch.

​
IBKR constraints reflected in the payload

IBKR TWS order submission uses placeOrder with a valid order id, and TWS reports order lifecycle through callbacks such as openOrder and orderStatus. That means the downstream router must own IBKR client id, order id allocation, callback reconciliation, and retry policy. TWS also has a Read Only API setting that prevents API order acceptance. The API here does not try to detect or bypass that setting; it only exposes routing hints for the execution service to validate.

​
Vertex Quant constraints reflected in the payload

The referenced Vertex Quant stack is paper-first. Live trading stays blocked until explicit gates, account allowlisting, risk controls, kill-switch behavior, tests, and operator signoff exist. Trade intents therefore include:
  • safeguards.mode: "paper"
  • safeguards.submit: false
  • order.transmit: false
  • required checks for idempotency, approval, sizing, risk limits, and kill-switch state

​
References