YOUR AGENTS, YOUR RULES
Money your Agents can use.
Boundaries only you control.
Define the budget once. When a mandate is active, the Arc contract enforces its executor, services, payment cap, total limit, and expiry.
No pending requests
Requests outside an active mandate will wait here for your decision.
No Agents configured
No activity yet
WHO CAN ACT
Your Agents
Start with what an Agent should do. Axblade suggests an editable setup, then binds the final permissions to an identity you approve.
Choose a job, then tune the boundaries.
Recommendations are transparent presets. Every service, limit, expiry, and exception rule stays editable.
Choose a starter job or an open-source project above to prepare your first Agent.
WHAT THEY CAN DO
Mandates
A mandate combines purpose, approved services, spending limits, time, and exception handling.
No mandates yet
Add an Agent first. Then define its services, spending limits, expiry, and exception rules.
WHEN YOUR RULES NEED YOU
Requests
Only exceptions require attention. Routine payments stay autonomous.
No requests need you
When an Agent asks to go beyond a mandate, the amount, purpose, and violated rule will appear here.
PURPOSE · POLICY · PROOF
Activity
A readable record of setup changes, requests, decisions, and settlement.
Agent setup, mandate changes, requests, approvals, and settlements will appear here after they happen.
PRODUCT PREFERENCES
Settings
Wallet, network, notification, and default exception behavior.
Connect a wallet you control
Use a browser wallet on desktop or WalletConnect on mobile. Axblade never asks for a recovery phrase.
Checking deployment
Axblade is checking the configured Mandate Vault on Arc.
Unaudited testnet code. Testnet USDC has no real-world value.Ask me before proceeding
Requests outside a mandate wait for your explicit decision.
No saved setup
Agents and mandate drafts are saved in this browser; signed mandate state is also recorded on Arc.