Strategy signals for integrators, and batch trade submission
Integrators holding a general key can now read the target-weight books of the copy-trading strategies Treasures publishes to them, ask for the orders that exit a book from one of their users' Solana wallets or rebalance it to the book, and submit up to 25 signed quotes in one request. Eight new routes, all additive; nothing changes for existing callers.
What changed
Strategy books, under a new Signals tag, general tik_ key only:
GET /signals/strategies: the catalog of strategies published to integrators, newest first, each with its latest book'sbook_hash,book_as_ofandsignal_id, so one call says which books changed.GET /signals/strategies/{id}: one strategy (id or slug) with its current book: every ticker and its weight,deployed_weight,cash_weightand abook_hashthat changes only when the weights move.as_ofis when Treasures ingested the book, not the filing date.GET /signals/strategies/{id}/history: past books as full weight vectors, newest first, with cursor paging.
Orders from a book, general key plus an ownership proof for the Solana wallet:
POST /signals-orders/exit/planandPOST /signals-orders/rebalance/planreturn the orders only, nothing quoted: the full-share sells that leave a book, or the sells and buys that bring the wallet's positions to it, with afundingblock that drives the two-round reshuffle. These are the default for human and hardware-wallet flows.POST /signals-orders/exitandPOST /signals-orders/rebalancereturn the same orders, each with its signable/quote/sellor/quote/buyanswer, for programmatic signers who can sign inside a Solana quote's window. They refuse a second call for the same wallet and strategy while an earlier call's quotes are live (409 orders_in_flight, withRetry-After).- Every orders route takes
expected_book_hashand refuses with409 book_changedwhen the book moved. Treasures never signs: each order is submitted throughPOST /trade/submitby the wallet's owner, as any trade is.
Batch submission, general key only:
POST /trade/submit/batchtakes up to 25POST /trade/submitbodies and answers each in request order with thehttp_statusand body the single route would have given. Same-chain Solana legs only, noquote_idtwice, and a body cap of 100 KB.
What to do
Nothing, unless you want the new routes: existing routes, bodies and responses are unchanged. The signals routes need a general integrator key; a read-only trk_ reporting key is refused. The agent skill does not cover these routes yet, so read Strategy Signals and the API Reference directly. The per-route key table on Integrator API Keys and the proof table on Ownership Proof list the new routes.