Zerion

Zerion

Unified API + CLI for crypto wallets across 14 EVM chains and Solana. The zerion binary ships from npm; this skill is the entry point for all Zerion capabilities. Capability and partner docs live in nested files and are loaded on demand.

Setup

Skills shell out to the zerion binary. Don't pre-install — try the command first. If a zerion invocation fails with command not found, install once:

npm install -g zerion-cli

Requires Node.js ≥ 20. The npm package is zerion-cli; the installed binary is zerion.

Authentication

Three modes. Pick one for analytics; trading always uses an API key.

A) API key (recommended)

export ZERION_API_KEY="zk_dev_..."

Get yours at dashboard.zerion.io. Dev keys begin with zk_dev_. Limits: 120 req/min, 5K req/day.

B) x402 pay-per-call (no signup, analytics only)

Pays $0.01 USDC per request via the x402 protocol. EVM (Base) or Solana.

export WALLET_PRIVATE_KEY="0x..."     # EVM (Base) — 0x-prefixed hex
export WALLET_PRIVATE_KEY="5C1y..."   # Solana — base58 keypair
zerion portfolio <address> --x402

# Or enable globally
export ZERION_X402=true

Both chains at once:

export EVM_PRIVATE_KEY="0x..."
export SOLANA_PRIVATE_KEY="5C1y..."
export ZERION_X402_PREFER_SOLANA=true   # optional

C) MPP pay-per-call (analytics only, EVM Tempo)

Pays $0.01 USDC per request via MPP on Tempo.

export TEMPO_PRIVATE_KEY="0x..."      # or reuse WALLET_PRIVATE_KEY
zerion portfolio <address> --mpp

# Or enable globally
export ZERION_MPP=true

Trading commands (swap, bridge, send) always use the API key + an agent token, regardless of ZERION_X402 / ZERION_MPP.

Capabilities — load on demand

Before executing any capability below, Read the matching file for the full command surface, flags, edge cases, and examples.

Pairing rules:

• Trading + signing require an agent token → see capabilities/agent-management.md first if user has none.
• Run analysis before trading to verify balances and positions.

Partner integrations — opt-in

These cover specialized flows on top of the core CLI. User must name the partner (or describe a flow that maps to one). Then Read partners/<name>.md.

Rule: never preload partner docs. Only Read when the user explicitly invokes the partner or asks for a flow that uniquely maps to it.

For authoring new partner integrations, Read partner-skill-creator.md.

Output contract

All commands emit JSON to stdout (default — agent-friendly). Errors emit structured JSON to stderr:

{ "error": { "code": "missing_api_key", "message": "..." } }

Flags: --json (default), --pretty (auto-enabled for TTY), --quiet.

Supported chains

ethereum, base, arbitrum, optimism, polygon, binance-smart-chain, avalanche, gnosis, scroll, linea, zksync-era, zora, blast, solana.

Solana supports same-chain swaps and bidirectional bridging to/from EVM chains. Cross-format bridges (Solana ↔ EVM) require an explicit destination via --to-wallet <name> or --to-address <addr> matching the target chain's format.

Command shapes:

• Same-chain swap: zerion swap <chain> <amount> <from-token> <to-token>
• Cross-chain bridge: zerion bridge <from-chain> <from-token> <amount> <to-chain> <to-token>

See capabilities/trading.md for the full flag reference.

Use zerion chains for the live catalog with metadata.

Common error codes

Key management

Wallets are encrypted with AES-256-GCM via the Open Wallet Standard (OWS) vault at ~/.ows/. Private keys never leave the device; signing happens locally. The Zerion API never sees keys.

~/.zerion/config.json (mode 0o600) stores agent tokens, default wallet, default chain, and slippage.

Resources

• API docs: developers.zerion.io
• Dashboard: dashboard.zerion.io
• x402 protocol: x402.org
• CLI source: github.com/zeriontech/zerion-ai

Source: zeriontech/zerion-ai — distributed by TomeVault.