Avici Money docs: wallet, secured Visa, virtual accounts

Avici Money (avici.money) is an internet-native crypto neobank: hold assets, spend via Visa, receive fiat into virtual accounts that convert to USDC. Canonical product docs live at docs.avici.money (full index: llms.txt; pages also as .md).

X: @avici. Agent surface (CLI/MCP) is covered in depth in Avici CLI and MCP for agents. This page maps the product architecture from the docs for builders integrating or comparing neobank patterns.

Click to zoom

Doc map (high signal)

Wallet architecture

• EVM: smart contract wallet via Zerodev — no traditional EVM private key; social login email is a signer; passkey required for tx approval
• Networks (docs): Ethereum, Polygon, OP, Base, Arbitrum, Avalanche, BNB, Monad, Mantle, Scroll (+ others as listed)
• Solana: receive/send/swap in-app; not AA — private key exportable from Settings
• Gas: Avici relayer sponsors EVM + Solana in many cases; not Ethereum mainnet (need ETH); Solana ~5 free txs/day then need SOL

Secured Visa card (core mechanic)

Issuer partner: Third National. Native card currency: USD. Model is secured credit, not unsecured unsecured bank credit:

1. User deposits USDC into a loan escrow contract
2. Matching USD credit appears on the Visa card
3. Spend reduces card credit balance
4. On a delay (docs: ~1–2 days, sometimes up to a week), spent USDC is liquidated from the contract to settle Visa

Custody claim in docs: escrow is user-owned; neither Avici, Third National, nor Visa controls the loan contract as owner. Avici can place a charge via spend attestation and only withdraw amounts linked to those charges; residual USDC withdrawable by the user wallet after spends.

Example (docs):
  deposit 100 USDC → $100 card credit
  spend $20     → $80 credit remaining
  settle later  → 20 USDC liquidated from escrow

Cards: virtual + physical; multiple cards for categories; Apple/Google Pay. Merchant reach: Visa international. Always re-check regions/prohibitions and restricted MCC lists before production spend assumptions.

Fees (cards — snapshot from docs)

Source: Fees and Limits. Numbers change — verify before quoting to users.

Virtual bank accounts

• USD & EUR virtual checking in user name (partner rails — intro docs cite Iron / Bridge)
• Receive salary/freelance/remittance-style fiat (ACH, Fedwire, SEPA — see rails page)
• Incoming fiat auto-converts to USDC into Avici wallet — not a place to park fiat long-term
• Only USD/EUR accepted for send-to-account flows per docs

Agent access (pointer)

CLI install + MCP setup, tool list, and desktop-only constraints: CLI & MCP article and docs CLI & MCP.

# Local CLI (desktop)
curl -fsSL https://avici.ai/install.sh | bash
# Hosted MCP setup
open https://mcp.avici.money/setup
# Docs
open https://docs.avici.money/

Read-only today: balances, holdings by network, card spend power, purchases, activity, refunds. No send/swap/withdraw/settings via agent.

Builder takeaways

Related: Solana neobank how to start · Crypto cards landscape.

Links

• docs.avici.money
• avici.money
• @avici
• Directory · Avici

Summary

docs.avici.money is the product source of truth for Avici’s neobank stack: Zerodev + Solana wallet, USDC-secured Visa (Third National) with user-owned escrow settlement, USD/EUR virtual accounts that mint spendable USDC, and a deliberately read-only agent CLI/MCP. Use the docs map for integration decisions; use the CLI/MCP article when wiring ChatGPT/Claude/terminal agents.