Skip to main content

Supported Services

Here is a quick overview of what you can do through Treasures. Everything below is available to any API caller unless it says otherwise; Compare Access Paths shows the same list by audience.

Discover assets​

Treasures allows users and integrations to discover a full list of supported tokenized assets, including asset symbols, names, supported networks, indicative pricing availability and trading availability.

A single ticker may be listed by more than one infrastructure partner, each on its own network, and availability is reported per listing rather than per symbol. Read the listing response rather than hardcoding a set. Partners bring assets online over time, and a listing can also carry a warning that it is currently thin or untradable.

Need everything the catalog knows about a single name? Company and ticker details returns the profile (description, sector, industry, website, logo) alongside every listing, the traditional-market snapshot, the pre- and post-market print, market session, analyst consensus and grades, next earnings and the latest news, in one call. It requires an integrator API key, and every block is best-effort: anything the upstream cannot supply comes back null rather than failing the call. For per-protocol on-chain prices keep using prices; this route deliberately does not carry them.

Wallet infrastructure​

Create or connect a self-custodial wallet and use it as your identity and permission layer across all Treasures services. Wallet access can be embedded into the user experience or connected through an external supported wallet provider.

Get quotes and execute trades​

Get live, time-limited execution quotes for any supported tokenized stock, then submit your transaction request for routing and execution. Treasures handles the routing to on-chain infrastructure automatically. Supports both buy and sell flows.

Pricing a trade you don't intend to execute (a screener, a widget, a what-if)? Use the price preview. It returns the same legs a buy quote would, with no wallet and no ownership proof, and nothing is persisted: there is no quote to submit and no status to poll. It requires an integrator API key precisely because it binds no wallet; the key is what identifies the caller. Previews are capped at 1,000,000 USDC and draw on a rate limit shared by every caller of the route, so honour Retry-After rather than retrying immediately. Re-quote through buy for anything you intend to sign.

Two chains also offer a speed route: a single on-chain swap that settles in one block instead of a relayed order. Ask for it with priority: "speed" on a buy or sell quote and you get back a complete unsigned transaction to sign, which Treasures broadcasts against your own wallet's native gas. It is available on Robinhood Chain and Base, and on Base it can be made gasless again through a sponsored user operation if you run an ERC-4337 stack. Under speed, a buy of a listing on a chain the wallet is not funded on can also come back as a single cross-chain leg, paid from the chain your stablecoin is on.

A sell can pay its USDC out on another chain: send payout_chain (sol, eth or base) on a sell quote and the proceeds of every position that can pay out there land in your own wallet on that chain, with no separate bridge step. The full tradeoff table and both cross-chain flows are in Routing and Priority Mode.

Portfolio and trade history​

Read your current holdings and trade history via the web app or API. Useful for building dashboards, reconciliation workflows or agent memory.

Portfolio snapshots refresh every 30 seconds (as_of, is_cached), so polling faster returns the same snapshot. Under heavy load the route can answer 503 portfolio_busy with a Retry-After header in seconds; sleep that long and retry the same request. A cached snapshot is never refused. Positions on Robinhood Chain and Base are read for every wallet when you send an integrator API key, and otherwise only for wallets Treasures already knows.

Settlement reporting​

Integrators holding an API key can read their organisation's settled trades, newest first, with cursor pagination. Only trades submitted with the API key presented are attributed to the organisation and appear here. A submit sent without the header is attributed to no one and cannot be recovered afterwards.

Keys come in two kinds, issued per organisation by the Treasures team. A general tik_ key reaches every route on the API. A read-only trk_ reporting key reaches the reporting routes and nothing else (today that is exactly this one) and answers insufficient_scope everywhere else, which is what makes it safe to hand to a third-party reporting partner. These routes require a key: this one, company and ticker details, the price preview and the payout routes, all but this one taking a tik_ key only. Every other route may be called anonymously, but a key you send is still verified and still earns your organisation attribution and its own rate bucket. The route-by-route table is on Integrator API Keys.

Deposits and withdrawals​

Move USDC into and out of your Treasures wallet (where supported). Deposit and withdrawal availability may depend on the asset, network, wallet type, integration channel and applicable compliance controls.