Agentic baskets

A frozen basket holds the same recipe forever. An agentic basket holds a recipe that an agent rotates over time toward what is working, and pays the trading surplus to holders in USDG. The token you hold is the same kind of fully-backed, redeem-anytime index. The difference is one narrow, bounded power: an agent key may call rebalance.

Everything on these pages is enforced by the BasketToken2 contract, not promised. The exact bounds are on the policy page; the payout mechanics on payouts; the pricing layer on oracles.

The live lineup

Three first-party pilots are live on Robinhood Chain mainnet, deployed through the public BasketFactory2 in July 2026, mintable and redeemable by anyone:

All three run the same on-chain policy — 1-day cooldown, ≤25% turnover and ≤1% slippage per rebalance, 0.30% mint fee — and pay holders through their own BasketDistributor on a 7-day cycle. Because the recipe rotates by design, these docs describe each pilot's strategy and policy, never a "current" composition: read the recipe live in the app or on Blockscout (constituents() / units() on the basket contract).

Anyone with a V2 curator license can publish their own agentic basket through the same factory — the pilots have no special powers.

What the agent can do

Exactly one thing: rebalance(legs, newTokens). It routes trades through whitelisted settlement contracts, then hands the contract a new set of constituents. The contract recomputes the recipe from the balances it actually holds and proves, on-chain, that the trade stayed inside the policy. If any check fails, the whole rebalance reverts and nothing changes.

What the agent can never do

The policy is carved in at deploy as immutable ceilings; the curator may choose stricter values, never looser. The agent has no path to mint, redeem, fees, custody, or the fee recipient. A compromised agent key can cost holders at most the slippage budget of NAV per cooldown window — by default 1% per day, measured on total NAV — by trading at bad prices. That is the entire blast radius, derived precisely on the policy page.

Redeem is never gated

Redemption is in-kind and reads no price feed. No role — not the agent, the curator, the guardian, or the protocol — can block it. The only thing that can stop a specific constituent from transferring out is that token's own issuer freezing it, a risk inherited from the token, identical to a frozen basket. See Risks.