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.

Learn

x402 agent payments treasury

x402 lets agents pay for API calls at request time, but payment for a tool call is not permission to move treasury funds.

Problem

Autonomous agents often need occasional treasury calls without a long API-key onboarding loop, but operators still need clear boundaries around live execution.

Stackit.ai solution

Stackit.ai uses x402 as a wallet-sovereign access path for priced calls while keeping transaction execution behind wallet signatures and user-approved automation permissions.

Integration

Agents can inspect /x402/prices.json, handle HTTP 402 challenges, attach X-Payment, and call REST endpoints. Public no-auth tests remain available for evaluation.

MCP server REST API x402

Safety

x402 pays for access. It does not bypass policy checks, LTV ceilings, idempotency, replay protection, or human approval for live fund movement.

Permissions Tool risk model

Trust

Agents can verify x402 prices, OpenAPI schemas, fees, status, and permission docs before relying on paid calls.

Trust Security Fees JSON

Common workflows

Inspect machine-readable x402 pricing before paying for a call.

Use public demo endpoints before sending an X-Payment header.

Preview a borrow over x402, then ask for a wallet signature separately.

Keep payment metadata free of unnecessary PII.

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.

Run sandbox test Agent landing page