Skip to main content

Manager API: dashboard sign-in, strategy and SMA account reads, self-service keys, and a reshaped fee ledger

The Manager API reference and guide now cover everything the API serves. It accepts a signed-in session on the Treasures dashboard alongside your manager API key, adds reads for the strategies assigned to you and for the separately managed accounts of an SMA strategy, and lets a dashboard session mint and revoke your keys. Two changes reach existing key callers and are marked Action: GET /fees has a new response shape, and a request with no credential now answers 401 unauthorized.

Speed sells fall back to the relayed route, and unlisted tickers leave the stocks reads

A priority: "speed" sell on Robinhood Chain or Base that the speed route cannot price is now quoted on its relayed route, with a new speed_route_fallback warning, where the position used to be left out or the quote refused. One Action item, for callers that send priority: "speed" on POST /quote/sell. Separately, a ticker that no venue lists a token for is no longer served by the stocks reads.

A size refusal names its minimum on mixed refusals

A 422 no_routes whose reason is amount_too_small now carries min_notional_usdc whenever a venue that refused for size has a known minimum above your order, even when other venues refused for another reason. Before, such a refusal could come back with the reason and no number. Additive: nothing to change.

Refusals that say why, firm Solana minimums, and BNB Smart Chain opens

A 422 no_routes that used to come back with no reason now says what happened, and names a minimum size where one is known. A priority: "speed" refusal lists the listings speed skipped, so you know a quote without priority may succeed. Solana minimums now come from quotes bound to a wallet, the kind a market maker honours. And BNB Smart Chain (bnb) is open for ondo and xstocks. Everything is additive on the request; the Action items matter only if you match reason or error_code against a fixed list.

Sponsored lane: a wallet's first trade can delegate it

On the sponsored lane (priority: "speed" with execution: "user_operation"), a wallet that has never been delegated on Robinhood Chain or Base can now trade from its very first operation there. The quote is served, and that first UserOperation carries the wallet's EIP-7702 authorization as eip7702Auth, so the delegation and the trade land in the same transaction. A caller whose wallet is already delegated sees no change.

A per-chain guide, and the Robinhood Chain approval address

Chains and Venues is a new page with each chain's rules in one place: the stablecoin it trades in, who pays gas, which approvals to send and to which address, which quote options it takes, its sessions and minimums, and the mistakes integrators hit most. It also corrects one rule: a Robinhood Chain trade needs a one-time approval, to an address of its own.

Pay Solana fees for your users, bridge between any two chains

A Solana wallet holding no SOL can now trade: send sol_fee_payer, a Solana wallet you fund, on buy and sell quotes and it pays the fees (a first buy of an ondo token is the exception). Bridging takes any two supported chains, with an optional mode where Treasures submits the deposit, and every quote leg carries its own expires_at. The reference also documents BNB Smart Chain, which is not open yet.

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.

Integrator fees and payouts

Integrators can now charge their own fee on the trades their users make through them, see it on every quote and settled trade, and claim it in USDC through four new routes under /payouts. All of it needs an integrator key.

Docs reorganised by audience

This site is now organised into Users, AI Agents and Enterprises tabs, with the API Reference and this changelog as tabs of their own.