Avici: crypto neobank balances for AI agents via CLI and MCP

Avici: crypto neobank balances for AI agents — connect ChatGPT, Claude, or a terminal agent to your account with a CLI or MCP URL, and let it answer money questions without permission to move funds.

Product home: avici.money. Docs: docs.avici.money. The agent entry point you linked is Avici CLI & MCP. X: @avici.

Click to zoom

What Avici is (before the agent glue)

Avici positions itself as an internet-native neobank on crypto: hold digital assets, spend globally, keep more ownership than a traditional bank app. The core pieces matter because the agent layer is a window into them, not a separate product.

• Avici Wallet — EVM side is a ZeroDev smart-contract wallet (social login + mandatory passkeys; no exportable EVM seed). Solana is also supported for receive / send / swap; that Solana key can be exported from Settings because it is not the same smart-wallet model.
• Secured Visa credit cards — deposit USDC into a self-custodial loan escrow; card gets matching USD spend power; spends liquidate USDC over time. Issued with Third National. Apple Pay / Google Pay supported.
• Virtual bank accounts — USD/EUR accounts (Iron / Bridge rails) so ACH, Fedwire, SEPA can land as auto-converted USDC into the Avici wallet.

Networks: multiple EVMs (Ethereum, Base, Arbitrum, Polygon, OP, and others listed in wallet docs) plus Solana. Stablecoin matrix for virtual-account rails includes USDT/USDC/EURC on Solana and major EVMs. Gas: Avici sponsors many EVM txs via its relayer (not Ethereum mainnet); Solana gets a small daily free tx allowance then needs SOL.

Every in-app money movement still wants a passkey. That design choice is why a read-only agent API is a natural first step.

Why CLI and MCP exist

Builders and power users already live in agents. Opening the mobile app to check “can I afford this subscription?” breaks flow. Avici’s agent surface lets ChatGPT, Claude, Codex, or Claude Code answer those questions from the same session where you are planning travel or debugging a bot.

Two connectors, same permission model:

You do not need both. Install both only if you hop between terminal agents and chat UIs.

What the agent can see (and cannot do)

Officially documented readable data:

• Total wallet balance
• Token holdings grouped by network
• Avici card details (CLI path)
• Available card spending power
• Recent card purchases
• Transaction activity
• Refunds

Explicitly not allowed through CLI or MCP today:

• Send or withdraw
• Swap or bridge
• Top up
• Transfer
• Approve transactions
• Change card or account settings

That is the right default for a neobank agent integration. Compare to spend-capable agent wallets (for example PayBox): Avici’s first agent cut is observability; PayBox’s is scoped execution. Different trust models — pick deliberately.

Example prompts from the docs:

What is my Avici wallet balance?
Show my holdings by network.
How much can I spend on my card?
Show my recent card purchases.
Have I received any refunds?
Show me my Avici account.

Path A — Avici CLI (terminal agents)

Guide: Adding Avici CLI to ChatGPT / Claude Code.

curl -fsSL https://avici.ai/install.sh | bash

The installer drops the CLI plus official skills for Codex and Claude Code. Login is QR-based: scan with the Avici mobile app, approve Creator Dashboard, wait until the CLI confirms.

Requirements: macOS or Linux, desktop agent or local terminal, Avici app already signed in. No mobile browser install path.

If the shell cannot find the binary:

$HOME/.avici/bin/avici version
# then restart the terminal / agent

Open a fresh agent session and ask it to show your Avici account. If the agent only returns a QR image path, tell it to render the QR inline.

Path B — Hosted MCP (chat agents)

Official MCP URL (only use Avici-published URLs):

https://mcp.avici.money/setup

Nothing to install locally. Auth is email + one-time code on Avici’s login page — never paste that code into the chat.

Claude

Guide: Adding MCP to Claude (beta). Customize → Connectors → add custom connector:

Name: Avici
URL:  https://mcp.avici.money/setup

Leave OAuth client advanced fields empty. Connect, complete email OTP, enable Avici on the chat’s connector menu, then ask for your account. Team/Enterprise: an Owner adds the org connector first; members link their own Avici accounts after.

ChatGPT

Guide: Adding MCP to ChatGPT (beta). Desktop browser, ChatGPT Work, developer mode on (Settings → Security and login). Create a personal plugin:

Name:           Avici
Description:    View your Avici wallet, cards, balances, spending, and refunds. Read-only.
Connection:     Server URL
Server URL:     https://mcp.avici.money/setup
Authentication: OAuth

Expect the “unreviewed MCP server” warning — Avici is not in the official plugin directory yet. After OAuth, start a Work chat, enable Avici from the + / More menu (or type @Avici).

Beta and platform constraints

• Custom MCP on ChatGPT and Claude is itself beta; menus and plan limits move.
• Free Claude accounts may only get one custom connector.
• Setup is desktop-only for both CLI and MCP. Mobile may or may not see the connector after the fact — do not plan onboarding there.
• Official directory plugins are “coming soon” per docs; until then, custom server is the supported path.

FAQ index: CLI & MCP FAQs.

How this fits a builder mental model

Think in three layers:

1. Banking product — wallet, card escrow, virtual accounts (passkey + app).
2. Read API for agents — CLI skills or MCP tools that expose balances and spend history.
3. Your automation — agents that budget, reconcile expenses, or draft finance updates using that read model.

Useful patterns today:

• Morning brief: “Holdings by network + card headroom + last 10 purchases.”
• Expense hygiene: “Any refunds pending? Any large card spends since Friday?”
• Multi-chain sanity: Solana USDC vs Base USDC without opening five explorers.

Not ready yet (per current docs): agent-initiated top-ups, auto-pay bills, or swap routing. If you need agent execution with grants and passkey gates, look at wallet products designed for that — and keep Avici as the consumer neobank + read plane until they ship write tools.

Solana notes

Solana is a first-class network inside the Avici app for transfer and swap, and it shows up in virtual-account stablecoin support (USDT/USDC/EURC). Agent views that group holdings by network will surface Solana balances alongside EVMs. Remember the custody asymmetry: EVM is smart-wallet/AA; Solana keys are exportable — treat device security accordingly.

Quick start checklist

1. Create and fund an Avici account in the mobile app; finish passkey setup.
2. Pick CLI or MCP based on where your agent runs (table above).
3. CLI: run the install script, scan QR, new session, “Show me my Avici account.”
4. MCP: add https://mcp.avici.money/setup, complete email OTP on Avici’s page only, enable the connector in a new chat.
5. Verify read-only behaviour: ask for balance, then confirm the agent refuses (or has no tool for) send/withdraw.

Resources

• avici.money
• Docs home · llms.txt
• CLI & MCP overview
• CLI install
• MCP → Claude · MCP → ChatGPT
• Wallet · Secured cards · Virtual accounts
• MCP URL: https://mcp.avici.money/setup
• PayBox (agent wallet with spend grants)
• Avici on DevRels

Bottom line

Avici’s agent story is refreshingly narrow: give coding and chat agents a trusted, read-only view of a real crypto neobank — multi-chain wallet (including Solana), Visa spend headroom, purchases, and refunds — without opening the blast radius of automated transfers. Wire it with curl … install.sh for terminal agents or https://mcp.avici.money/setup for Claude and ChatGPT, keep OTP off the chat transcript, and treat write-capable agent finance as a separate product decision until Avici ships it.