What changed​

Sells: payout_chain

• POST /quote/sell accepts payout_chain ("sol", "eth" or "base"; absent or null keeps the old behaviour). The sale's USDC lands on that chain, in your own wallet there. A sol/xstocks, base/coinbase or eth/ondo position held on another chain sells cross-chain as one leg, marked by payout_chain on the leg, whatever the priority. A position that cannot pay out there is left out with a cross_chain_route_unavailable warning and is never sold on its own chain instead.
• You fund the network gas for a cross-chain sell leg on the position's own chain (gasless: false), unless your paymaster sponsors it on the execution: "user_operation" lane. On Ethereum and Base it is two signed transactions, an exact-amount approve then a deposit, or one evm_calls payload under execution: "user_operation". On Solana it is one versioned transaction.
• GET /quote/{quote_id}/status legs gain payout_chain and payout_tx_hash. On completed, payout_chain names where the USDC actually landed, which is the sale's own chain if the payout was returned there.
• GET /settlements reports such a sale as two transactions: the sale (sending) and the payout (receiving).
• New refusals: 400 invalid_request with a payout_chain: message prefix, and 422 no_routes with reason: "payout_route_unavailable".

Buys: cross-chain speed legs

• Under priority: "speed", POST /quote/buy and POST /quote/preview may quote a stock you are not funded on as a cross-chain leg instead of dropping it. The leg carries origin_chain (where your stablecoin leaves from; chain stays the destination), cross_chain_cost_bps and cross_chain_cost_usdc, and base_asset names the origin's currency.
• chain: ["eth"] with "speed" on a buy or preview now returns a cross-chain leg or 422 no_routes instead of an unconditional 400.
• New warnings[] codes cross_chain_route_unavailable and cross_chain_price_deviation, a new no_routes reason cross_chain_wallet_missing, and new per-leg error_codes refunded, deposit_reverted, delivered_other_currency, cross_chain_unsettled and a per-leg quote_stale.

Also

• cost_breakdown_bps.dex_swap_fee_bps is nullable: null only on a cross-chain leg.
• Chain gains arbitrum and Protocol gains reality, for an upcoming venue; the reality listings block on GET /stocks and GET /stocks/tickers is null until it opens.
• GET /quote/{quote_id}/status asks for poll_after_ms: 3250 (was 10250) when only gasless or Solana legs remain.
• An on-chain venue price more than 1.5x away from the reference market price reads share_price_usd: null on GET /stocks/{ticker}.

What to do​

Action (strict response parsers only): accept null for cost_breakdown_bps.dex_swap_fee_bps. A caller that sends neither priority: "speed" nor payout_chain never receives it.

Nothing else is required. Buying and Selling maps every combination of priority, execution and payout_chain to the legs it returns and how to sign each one. To use the new routes, update to skill 1.16.0 (Agent Skills) or read the API Reference. Routing rules: Routing and Priority Mode.

What changed​

• Your fee on every quote made with your key. Treasures configures a default fee and a ceiling for your key; send integrator_fee_bps on POST /quote/buy, POST /quote/sell or POST /quote/preview to use a different fee on one quote. Each leg reports it as cost_breakdown_bps.integrator_fee_bps, and estimated_output_* already allows for it.
• Submit with the key that quoted. A quote that carries your fee is refused at POST /trade/submit with 403 quote_integrator_mismatch if it arrives without that key.
• New quote refusals: 400 invalid_integrator_fee, 400 integrator_fee_requires_api_key and 503 integrator_fee_misconfigured.
• Settlements: GET /settlements gains an integrator_fee entry in fee_costs, with the payout_id it went out in, and two filters, payout_id and payout_status.
• Payouts, general tik_ key only: GET /payouts/accrued (what you are owed and whether you can claim it), POST /payouts (claim all of it to your registered address; Idempotency-Key required), GET /payouts and GET /payouts/{payoutId}.

What to do​

Nothing, if you do not charge a fee: a quote without your key is unchanged, and with it your configured default applies. To charge or claim fees, read Integrator Fees and Payouts, and always submit fee-carrying quotes with the key that requested them.

What changed​

• A dedupe_key beginning with replan: or catchup:, in any letter case, is refused with 400 invalid_request and the message names the field. Every other key up to 200 characters is accepted as before.
• Documented on the dedupe_key request field and in Managing a Strategy.

What to do​

Action: if any key you publish starts with replan: or catchup:, rename it. Keys that never used those prefixes need no change.

What changed​

• New API surface at https://api.treasures.io/manager/v1, documented in the Manager API reference with a guide at Managing a Strategy.
• POST /strategies/{strategyId}/signals publishes the whole book you want followers to hold: 1 to 200 tickers with decimal-string weights summing to at most 1, the remainder held as cash. A required, caller-chosen dedupe_key makes retries safe: a repeat returns 200 with the original signal and rebalances nothing. The response tells you which session the book executes in (urgency, trading_day, ttl_at).
• GET /fees returns what you are owed, what is pending and what has been paid, your recent payouts and a paged list of the collections behind them.
• Credential: a manager API key (cmk_…) in X-API-Key, mandatory on every route, issued once by Treasures and not retrievable afterwards. 60 requests per minute per manager.

What to do​

Nothing changes for callers of the B2B Public API or the delegated wallet API. If you manage a strategy on Treasures, ask your Treasures contact for a key and a strategy assignment, then start from Managing a Strategy.

What changed​

• Each audience has its own tab with a short sidebar: Users, AI Agents and Enterprises.
• New reference pages: Compare Access Paths, Routing and Priority Mode and Integrator API Keys.
• The AI Agents tab points at the agent skills rather than mirroring them: Agent Skills covers what each skill does, how to install it and how versioning works. A machine-readable navigator is served at /skill.md.
• Search is available from the header.

URLs​

The agent guide moved from /overview/integrating-your-agent to /agents/integrating-your-agent. Every other page keeps its URL.

What changed​

• GET /portfolio can answer 503 portfolio_busy with a Retry-After header (delta-seconds) when the server is already computing as many fresh snapshots as it safely can and yours was not cached. Sleep Retry-After and retry the same request. A cached snapshot is never refused.
• Rate limits on GET /portfolio. Anonymous calls have their own per-IP row (600 per minute). With a general tik_ key the route is not bucketed by IP at all; the per-organisation bucket is the bound, sized for one request every 5 seconds per active end user.
• The blanket per-IP ceiling across all endpoints is now set per environment, always at or above the per-endpoint limits, and no longer covers /portfolio.
• Portfolio snapshots refresh on a 30-second cadence (as_of, is_cached). Polling faster returns the same snapshot.

What to do​

Nothing is required. If your client has a generic transient-error branch, add 503 portfolio_busy to it and honour Retry-After. Keyed integrators polling many end-user wallets should pace to the organisation bucket rather than spreading across IPs.

Details: Integrator API Keys and the API Reference.

That file covers every release from the API's launch, newest first: the Robinhood Chain and Base venues, tradability advisories, the chain set, foreign listings, quote warnings and the acknowledgement token, priority mode and the speed route, the wallet-less preview, ticker details, the sponsored user-operation lane, and the /portfolio identity gate. Entries that needed action from an integration are marked Action there, the same convention this changelog uses.

From 2026-09-19 onward, every change to the public API surface gets its own entry here.