Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(orders): document any-token orders, ladders, OCO and the preview-then-confirm MCP flow, with a changelog entry

nirholas7318a1c466e0
diff --git a/data/changelog.json b/data/changelog.json
index 6df6bfc44..f9e0c9274 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,15 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-10-23",
+ "title": "Limit, stop, trailing, ladder, OCO and DCA orders on any Solana token, from any MCP client",
+ "summary": "Agent orders are no longer limited to pump.fun tokens. Any SPL token can carry a limit, stop, trailing stop, ladder of take-profit levels, OCO pair or DCA schedule, filled through Jupiter or PumpSwap on the same audited path (spend policy, kill switch, rug firewall, one idempotency key per slice, per-agent lock). MCP clients get order_preview and dca_preview, which return what would be placed and when, then create tools that only accept the signed preview plus an explicit confirm flag. Each agent has an order book showing the next fire time and a plain reason for every skip, and you are notified when an order fires, fails or expires. The two DCA systems are now one store, and existing schedules were migrated intact.",
+ "tags": [
+ "feature"
+ ],
+ "link": "/docs/mcp"
+ },
{
"date": "2026-10-23",
"title": "Backtests now prove they are free of look-ahead and can be repeated",
diff --git a/docs/mcp.md b/docs/mcp.md
index a64ede9fe..0f35ffa9a 100644
--- a/docs/mcp.md
+++ b/docs/mcp.md
@@ -1469,6 +1469,17 @@ merchant and by day, from the package's local append-only ledger
---
+### Orders and DCA on any SPL token
+
+The threews-agent server places resting orders and DCA schedules from the agent wallet on any Solana token, routed through Jupiter or PumpSwap by liquidity. Every create is two steps so a model can never place anything the owner did not see:
+
+1. `order_preview` (limit, stop, trailing, ladder of up to 8 limit levels, or an OCO pair) or `dca_preview` returns the live price, whether it would fire now, the venue, the firewall verdict, the spend limits, when it acts, and a signed `preview_id` (ten minutes, single use, bound to the agent).
+2. After the user says yes, call the matching create tool (`limit_order_create`, `stop_order_create`, `trailing_order_create`, `ladder_order_create`, `oco_order_create` with `confirm_order: true`, or `dca_create` with `confirm_dca: true`) with that `preview_id`.
+
+Read and manage: `limit_order_list`, `limit_order_history`, `order_book` (next fire time and the reason for every skip: price outside band, cap hit, venue unhealthy), `dca_list`, `limit_order_cancel`, `dca_cancel`. Orders can carry an expiry, a price band and an OCO group; the owner is notified when an order fires, fails or expires. `dca_list` covers both rails: Solana schedules and EVM delegation schedules share one store (`orders`, rail `evm`), and the legacy `/api/dca-strategies` routes are adapters over it. Existing `dca_strategies` rows were copied by migration `20261010210000_orders_any_token.sql` without losing a schedule.
+
+Every fill runs the audited path in `workers/agent-orders`: spend policy, kill switch, rug firewall, an idempotency key per slice, and the per-agent lock. Creating requires the `wallet:write` scope and a signed real-funds agreement.
+
## Resources
Every hosted server publishes live, read-only views of your account as MCP resources under the `three://` scheme. Clients that render resources (Claude Desktop's attachment picker, Cursor, most agent frameworks) list them with `resources/list`; the per-agent entries are expanded for your 25 most recent agents, and the rest are available as templates from `resources/templates/list`. Every resource is JSON (`application/json`); append `?format=markdown` to the URI, or send `"accept": "text/markdown"` in the `resources/read` params, for a readable `text/markdown` rendering.
diff --git a/workers/agent-orders/README.md b/workers/agent-orders/README.md
index 88bcb182f..ec075beed 100644
--- a/workers/agent-orders/README.md
+++ b/workers/agent-orders/README.md
@@ -24,6 +24,10 @@ call that one audited path. Every fill is firewall-gated, capped by the agent's
spend policy, and written to `agent_custody_events` (the canonical spend ledger),
with an `order_fills` receipt linking back to it.
+## Any SPL token, ladders, OCO and the order book
+
+Orders are not limited to pump.fun mints. Each fill picks a venue (Jupiter or PumpSwap) from live liquidity and runs the same audited executor. Beyond single orders the engine supports ladders (several take-profit levels in one call), OCO pairs (one fill cancels its sibling), expiry, price bands, and a per-agent order book (`api/_lib/order-book.js`) that reports the next fire time and one closed-vocabulary skip reason per order. The sweep notifies the owner when an order fires, fails, expires or starts waiting. MCP tools and the preview-then-confirm contract: [docs/mcp.md](../../docs/mcp.md) ("Orders and DCA on any SPL token"). Tests: `tests/orders-any-token.test.js`, `tests/orders-engine.test.js`, `tests/agent-orders-sweep.test.js`.
+
## Order lifecycle
`active → firing → filled` (price/conditional, single fill) ·