@okxweb3/a2a-node 0.2.9 → 0.2.10-beta-98689bff7a-260826143751
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.
- package/README.md +26 -0
- package/dist/cli.js +1246 -262
- package/dist/index.js +1042 -211
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -161,6 +161,32 @@ okx-a2a xmtp-send \
|
|
|
161
161
|
--message <content>
|
|
162
162
|
```
|
|
163
163
|
|
|
164
|
+
## Signal trading demo
|
|
165
|
+
|
|
166
|
+
Publish one standard `TradingSignalV1` JSON object through the running daemon:
|
|
167
|
+
|
|
168
|
+
```bash
|
|
169
|
+
okx-a2a signal publish \
|
|
170
|
+
--service-id polymarket-demo-v1 \
|
|
171
|
+
--file ./signal.json \
|
|
172
|
+
--json
|
|
173
|
+
|
|
174
|
+
node strategy.js | \
|
|
175
|
+
okx-a2a signal publish --service-id polymarket-demo-v1 --stdin --json
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
Provider routes and Buyer risk policy are read from
|
|
179
|
+
`<OKX_AGENT_TASK_HOME>/signal-trading/config.json`. The provider daemon maps
|
|
180
|
+
`serviceId + subscriptionId` to a configured `jobId` and Buyer agent, then
|
|
181
|
+
sends `payload.type=signal` through the existing XMTP task group. The Buyer
|
|
182
|
+
handles verified signal messages without AI/LLM dispatch and can invoke the
|
|
183
|
+
official Polymarket CLI after local subscription and risk checks pass.
|
|
184
|
+
|
|
185
|
+
See [`examples/signal-trading`](../../examples/signal-trading) for provider and Buyer
|
|
186
|
+
config samples plus an ASP publishing script. Buyer execution defaults to an
|
|
187
|
+
explicit `DRY_RUN`; use `LIVE` only after wallet, balance, approvals, route,
|
|
188
|
+
token allowlist, and generated order arguments have been verified.
|
|
189
|
+
|
|
164
190
|
## User attention
|
|
165
191
|
|
|
166
192
|
User-facing notifications and decision requests are stored in
|