@liquiditytech/rapidx-cli 1.0.34 → 1.0.36

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -15,6 +15,14 @@ The canonical source is `rapidx schema --json` or `rapidx/tools`.
15
15
  - `rapidx/order/cancel-preview`: explicit alias for `order.cancel` preview. Submit `rapidx/order/cancel` with unchanged parameters, `previewId`, and `continueConsentId=confirmation.submitToken`.
16
16
  - `rapidx/trade/preview`: generic preview for write operations without a dedicated order preview command, including position writes, portfolio writes, and algo writes. Pass `targetCapabilityId`, then submit the target tool with unchanged parameters, `previewId`, and `continueConsentId`.
17
17
 
18
+ ## Automation Session Tools
19
+
20
+ - `rapidx/automation/start`: create a bounded local automation session after the user authorizes symbols, per-order max notional, total max notional, duration, actions, and order types. Input must include `explicitUserConsent=true` and `acceptedRiskText` from the user's authorization.
21
+ - `rapidx/automation/list`: list local automation sessions in the current workspace.
22
+ - `rapidx/automation/status`: read one automation session by `automationSessionId`.
23
+ - `rapidx/automation/extend`: extend an active session after user authorization. Input must include `explicitUserConsent=true` and `acceptedRiskText`; it cannot expand symbols, actions, order types, or notional limits.
24
+ - `rapidx/automation/stop`: stop a session. It blocks future automation previews/submits and does not cancel existing orders.
25
+
18
26
  ## Read Tools
19
27
 
20
28
  - Market reads: ticker, orderbook, klines, funding rate, mark price, symbol info, and open interest.
@@ -59,8 +67,7 @@ Preview ids are runtime-local. A preview created by MCP must be submitted throug
59
67
 
60
68
  Order identifiers use two validation layers. If `orderId` is provided, RapidX validates it locally as a 16-digit numeric id and returns `INVALID_INPUT` before any upstream call when the format is wrong. If `clientOrderId` is provided instead, do not apply `orderId` validation. For `order.query`, `order.replace-preview`, and `order.cancel-preview`, a syntactically valid `orderId` or `clientOrderId` is checked through RapidX readback; missing or non-open orders return `NOT_FOUND` or `BLOCKED` depending on the observed state.
61
69
 
62
- For automation, keep preview-first execution. Set `automationMode=true` and pass the user's exact `automationConsentText` only when the user has explicitly enabled RapidX automation mode in chat. The preview response still returns `confirmation.submitToken`; automation mode only means the agent may use that submit token without asking for another per-order chat confirmation within the authorized scope.
63
- Automation support is verified at the preview layer: valid automation input returns an `automation` object with `confirmationMode="automation-preview"`, while missing or generic `automationConsentText` is blocked before submission.
70
+ For automation, keep preview-first execution. Create an automation session with `rapidx/automation/start` after the user authorizes the scope, then pass `automationSessionId` into `rapidx/order/place-preview`, `rapidx/order/replace-preview`, or `rapidx/order/cancel-preview`. A valid automation preview returns `automationSession.confirmationMode="automation-session"` plus `confirmation.submitToken`; the agent may submit that preview without asking for another per-order chat confirmation. The submit call still uses the same business parameters plus `previewId` and `continueConsentId=confirmation.submitToken`. Automation sessions cover the order lifecycle when `allowedActions` includes `order.place`, `order.replace`, and `order.cancel`: place consumes notional by `maxNotional`, replace consumes the replacement order notional, and cancel consumes no notional.
64
71
 
65
72
  For TPSL or conditional algo orders, use `rapidx/trade/preview` with `targetCapabilityId="algo.place"`, then submit `rapidx/algo/place`. `conditionType="ENTIRE_CLOSE_POSITION"` may use `orderType="MARKET"` without `quantity` or `amount`; provide at least one take-profit or stop-loss trigger and verify with `rapidx/algo/open-orders`.
66
73
 
@@ -1,25 +1,25 @@
1
1
  {
2
- "version": "1.0.34",
2
+ "version": "1.0.36",
3
3
  "artifacts": [
4
4
  {
5
5
  "name": "rapidx-mcp-registry",
6
6
  "path": "packages/distribution/registry/rapidx.mcp.json",
7
7
  "channel": "offline",
8
- "checksum": "sha256:0a21dd7e9627c0996ed56d7409f28f0ca0d30de9d13c6b10650a7ef3fb67505b",
8
+ "checksum": "sha256:c4ad866ffd5864306ee2e2676042190594404b0731360bbb29e2bd8361f62857",
9
9
  "status": "ready"
10
10
  },
11
11
  {
12
12
  "name": "rapidx-quickstart-doc",
13
13
  "path": "packages/distribution/docs/quickstart.md",
14
14
  "channel": "offline",
15
- "checksum": "sha256:e7cb18db9ce37a94ff1489d951f23b5f0407fd9e1f28f47f8ec13681f5760ccc",
15
+ "checksum": "sha256:6dfc7d5efad6dce3bd52d27735fd0d3e57420cffa4d48a432f8d4e35058e6741",
16
16
  "status": "ready"
17
17
  },
18
18
  {
19
19
  "name": "rapidx-tools-doc",
20
20
  "path": "packages/distribution/docs/tools.md",
21
21
  "channel": "offline",
22
- "checksum": "sha256:59246ef27a9b826bfdc8a20c1ccd8ec6556a95a00b7e5f71fb82d01eb1585b22",
22
+ "checksum": "sha256:bb5387983966306379001228b99e959cd80b7835ca615d8d567b3fddb7e129c8",
23
23
  "status": "ready"
24
24
  }
25
25
  ]
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "rapidx",
3
3
  "packageName": "@liquiditytech/rapidx-cli",
4
- "version": "1.0.34",
4
+ "version": "1.0.36",
5
5
  "command": "rapidx",
6
6
  "args": ["mcp", "serve"],
7
7
  "launchCommand": "rapidx",