Use Case

Agent wallet management

Agent wallet management is easier when the wallet has treasury policy, risk checks, and approval boundaries around it.

Problem

A wallet can receive assets and sign transactions, but an agent still needs to know what is safe, what costs money, what requires approval, and how to recover if the app is unavailable.

Stackit.ai solution

Stackit.ai works above the wallet. It exposes treasury state, policy state, fee rules, borrow previews, and unsigned transaction preparation while the wallet keeps signing authority.

Integration

Use MCP for natural tool calls, REST for programmatic wallet workflows, and x402 for wallet-sovereign agents that pay per request.

Safety

The wallet signs. Stackit.ai prepares, simulates, and enforces rules. Agents do not get unrestricted permission to move funds.

Trust

The permissions model, self-rescue runbook, fees JSON, and OpenAPI file give builders an auditable integration path.

Common workflows

Read wallet-linked treasury state before any proposed action.
Reject an unsafe borrow before a transaction is signed.
Use policy state to decide whether the agent should ask for approval.
Relay a transaction only after the wallet has signed it.

Test before you integrate

Run a public sandbox test, copy curl, inspect raw JSON, and verify that real execution remains gated by user-approved permissions.