Recipients
Where funds may be sent.
A planned authorization model for financial agents on Solana, with defined recipients, spending allowances, permitted actions, and approval conditions.
Explore Planned Workflows ↗
Where funds may be sent.
How much an agent or workflow may spend.
Which financial operations are permitted.
Which requests require a separate user decision.
When the authorization begins and ends.
The financial enforcement architecture remains in development.
Prepare and execute separately authorized payments to approved contributors.
Manage repeated payments within approved amounts, recipients, and schedules.
Track balances and upcoming commitments, with proposed actions available for review.
Assign allowances to financial tasks and approved destinations.
A team authorizes payments to five contributors within a specified budget.
The proposed recipients and amounts are checked against the mandate. A new recipient or an amount outside the allowance requires an additional decision before execution.
This example describes intended behavior. It is not a demonstration of a live financial service.
The endpoint containment agent and the financial AI agent serve different purposes.
A signature authorizing containment or release must not grant financial permissions. Any integration between the products must preserve separate authorization and clearly documented behavior.
Financial transactions remain subject to execution, liquidity, market, and protocol risks.
Permission controls define authorized activity. They do not guarantee transaction outcomes or reverse completed transactions.