Skip to main content
Preview Plutus is a white-label financial agent built on AgentKit, for platforms that don’t have an agent of their own. Banks, wallets, exchanges, custodians and fintechs embed it in their own product, and the platform keeps its brand, interface, custody, policies and signing throughout. A user can ask what they own, see how their portfolio is performing, discover and compare opportunities, get a personalized recommendation, approve an action and monitor the result, all in one conversation. Plutus runs on the same production infrastructure as every Yield.xyz integration. Plutus is in private preview. You can try the reference agent at plutus.yield.xyz.

What Plutus does

1

Portfolio view

Plutus builds a live view of balances, positions, rewards, idle assets and portfolio changes across the user’s connected wallets and networks, so it answers questions about the user’s actual portfolio.
2

Opportunity comparison

The agent reasons over normalized, execution-ready data across 4,000+ opportunities on 85+ networks: staking, lending, vaults, DeFi and tokenized real-world assets such as Treasuries and money market funds. It compares them on live APY, TVL, liquidity, historical performance, risk and exit conditions. Yield is broken down by source, and risk ratings from Credora and Staking Rewards are normalized into one schema where they exist.
3

Reasoning and recommendations

Plutus identifies idle assets, explains what changed in a portfolio, surfaces relevant risks and recommends how to allocate or rebalance. Every recommendation shows its reasoning, trade-offs and credible alternatives, so users get an argument they can check.
4

Transaction orchestration

Once the user approves, Plutus prepares and validates deposits, withdrawals, stakes, claims and rebalancing transactions, then routes them through the platform’s existing wallet, approval and signing infrastructure. Inputs are validated before a transaction is built, and Shield can check each transaction before it is signed.
5

Ongoing management

After execution, Plutus keeps monitoring positions, rewards, rates, lockups and risk, and prompts the user to claim, rebalance or exit when something changes.
For example, a user opens their wallet and asks Plutus to review their portfolio. Plutus spots an idle USDC balance, finds suitable opportunities across several networks, compares expected return and risk, recommends an allocation, prepares the transaction for approval and then monitors the position.

Guardrails and custody

Each deployment defines what Plutus can do, and these limits are enforced by the infrastructure around the agent, so a prompt cannot change them:
  • Transaction and spending limits
  • Approved assets and networks
  • Contract allowlists and method-level restrictions
  • Human-approval requirements
Policies can optionally be enforced inside a Trusted Execution Environment. Workflows can be semi-autonomous, where every action is approved, or autonomous within predefined policies. The platform keeps custody, approvals and signing. Plutus never touches private keys: every transaction stays unsigned until it reaches the platform’s wallet or MPC infrastructure. The same architecture runs in production with Privy, where Privy enforces spending limits, allowlists and approvals before signing, and with Coinbase x402, which lets an agent with a wallet pay for and call Yield.xyz tools without API-key onboarding.

Plutus or AgentKit

Plutus and AgentKit expose the same Yield.xyz infrastructure in two ways.

In your product

Plutus points out idle balances and recommends where to allocate them, and the fees you set apply to the positions your users open. After a transaction, it keeps monitoring the position and prompts the user when something changes. Users stay inside your product the whole time.

Get access

Plutus is in private preview. Try the reference agent at plutus.yield.xyz, and contact hello@yield.xyz to embed it in your product.

Next steps

AgentKit

Build your own agent on the same foundation.

MCP server

The tools Plutus and AgentKit call.