Skip to content

feat: add zerion-0x skill#74

Merged
graysonhyc merged 1 commit into
zeriontech:mainfrom
jlin27:jlin/add-zerion-0x-skill
May 18, 2026
Merged

feat: add zerion-0x skill#74
graysonhyc merged 1 commit into
zeriontech:mainfrom
jlin27:jlin/add-zerion-0x-skill

Conversation

@jlin27
Copy link
Copy Markdown
Contributor

@jlin27 jlin27 commented May 14, 2026

What it enables

The zerion-0x skill teaches AI agents how to execute token swaps via the 0x API (Swap
API v2 and Gasless API v2) directly from within Zerion Agent. An agent that hears "swap
500 USDC for ETH on Base via 0x" or "get me a gasless quote for 1000 ARB → USDC on
Arbitrum" can walk through the full price → quote → execute flow — choosing the right
signing path (AllowanceHolder, Permit2, or Gasless) for the user's context.

Zerion CLI commands it composes with

  • zerion wallet list — look up the taker address before fetching a quote
  • zerion analyze — pre-flight balance check before swapping

Why the combination is useful

0x's Swap API v2 aggregates liquidity across 20+ EVM chains and exposes three swap flows:
AllowanceHolder (simplest; works with multisigs and smart contract wallets), Permit2
(time-limited approvals, EIP-712 signing), and Gasless (fee deducted from sell tokens —
no ETH needed). The live 0x-mcp MCP server keeps the agent grounded in current endpoint
behavior, token addresses, and error codes at runtime. Zerion CLI provides the wallet
and portfolio layer on either side. Together: an agent can check balances, fetch a firm
quote, walk through the right approval + signing steps, and confirm the swap — without
leaving the CLI context.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@jlin27 jlin27 changed the title Add zerion-0x skill feat: add zerion-0x skill May 14, 2026
@graysonhyc graysonhyc merged commit e89f01a into zeriontech:main May 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants