What happens if Bitcoin crashes?

Stackit.ai's rules engine auto-repays your loan to keep your LTV in a safe range. Worst case is less borrowing power — not losing your BTC. The system is designed to protect your position, not liquidate it.

How much does Stackit.ai cost?

Stackit charges 2% on deposits, 2% when USDC converts into BTC or ETH, and 2% per borrowing execution — including the automated re-leverage cycles that rebuild your position as prices recover. Everything that protects you or pays you back is free: auto-repay, deleveraging, parking, selling to USDC, repaying, withdrawing, and leaving.

Is my crypto safe with Stackit.ai?

Stackit.ai operates on a self-custody model — your assets stay in wallets you control. You hold your own keys. Built on Privy and Bridge (both owned by Stripe) across Base, Arbitrum, and Polygon — trusted, institutional-grade infrastructure.

What if I stop depositing?

Your Health Score adjusts and Stackit.ai shifts to defense mode. The system protects what you've already built. You can resume deposits anytime.

Can AI agents use Stackit.ai?

Yes. Stackit.ai provides API access for AI agents with hard limits. Agents can deposit and spend within the same safety rails as human users. Both humans and AI agents use the same protected system.

Is Stackit.ai the same as STACKIT or StackAI?

No. Stackit.ai (stackit.ai) is a crypto treasury management platform for businesses. STACKIT (stackit.cloud) is a European cloud provider by Schwarz IT (Lidl/Kaufland parent). StackAI (stack-ai.com) is a no-code AI workflow builder. These are three completely different companies.

← Docs

Self-Rescue

Recover without the Stackit.ai UI.

This runbook explains how a user or operator can reduce debt, withdraw assets, and revoke future automation permissions directly if Stackit.ai is unavailable.

Last updated June 25, 2026

Warning

Direct protocol recovery is powerful and risky. A wrong chain, wrong asset, bad approval, rushed withdrawal, or misunderstood debt state can worsen a position. Use read-only checks first, keep transaction hashes, and ask for help when uncertain.

Supported recovery surfaces

Wallet assets

BTC, ETH, and USDC balances that remain in wallets the user/operator controls.

Aave positions

Borrowing positions on supported Aave V3 markets, currently documented around Base and Arbitrum.

Automation permissions

Future Stackit.ai automation authority granted through user-approved permissions or signer policy.

Plain-English version

Pause before acting. Direct protocol actions can create tax, liquidation, slippage, or signing risk.
Open the wallet that owns the treasury position.
Check current collateral, debt, LTV, and chain.
If there is debt, repay enough USDC directly through the lending protocol to move the position into a safer range.
After debt is reduced, withdraw collateral directly from the protocol if needed.
Revoke future automation permissions from the wallet or policy manager.
Save transaction hashes and contact support if anything looks inconsistent.

Technical version

Identify chain and market	Use wallet history, policy state, Aave dashboard, or block explorer to confirm Base or Arbitrum and the relevant Aave V3 market.
Read account data	Use Aave UI, a block explorer, or read-only calls to inspect total collateral, total debt, health factor, and available borrows.
Emergency repay	Approve USDC to the Aave pool if needed, then call repay for the debt asset and amount. Prefer over-repay only if the protocol and wallet UI make refund behavior clear.
Emergency withdraw	After health factor is safe and debt is reduced, call withdraw for the collateral asset and amount. Do not withdraw collateral first when debt remains fragile.
Revoke permissions	Remove delegated signer/session/policy permissions from the wallet account or smart-account policy surface. Revoke token approvals that are no longer needed.
Audit trail	Record tx hashes, timestamps, assets, amounts, wallet address, and the reason for every emergency action.

Contact support

Email support@stackit.ai with wallet address, chain, transaction hashes, and the action you are trying to complete. Do not send seed phrases, private keys, raw credentials, or one-time codes.