Any wallet works
Geodesics is wallet-agnostic; the same API key serves every kind. Start from whichever describes you:Your own wallet
Any raw key, from any agent stack, or a fresh one
geodesics init creates for you. The
wallet onboards itself during its first swap from each chain, gasless; nothing to activate.Virtuals ACP agent
First-class support for the wallet and swapping signer your agent already has. Nothing new
is deployed and no keys are handed over.
Your users' wallets
Building an app where each user brings a wallet? Your backend holds the API key; users sign
from any embedded or server-side wallet stack.
Four ways to integrate
All four run the same swap engine. Pick the one that fits, easiest first.1
Agent skill
The recommended way in. Tell your coding agent
Setup Geodesics swaps. Use https://geodesics.ai/llms.txt as reference and it installs the
CLI and guides the whole setup. The one step you run yourself is geodesics init, so your
credentials stay in your own terminal. Once set up, a packaged SKILL.md lets the agent swap
unattended in runtimes like Claude Code and Cursor. Details on the
Agent skill page.2
CLI
npm i -g @geodesics-protocol/cli gives you a geodesics command. One line per swap, with
token and chain aliases and automatic onboarding. Start at the Quickstart and
see the CLI page for every command and flag.3
TypeScript SDK
@geodesics-protocol/sdk for server-side platform integrations. swap()
runs the whole flow with one signature, and granular methods let you build your own retry or
signing pipeline. Slots straight into a Virtuals ACP agent’s existing wallet and signer.4
REST API
The raw wire for any language or a fully custom client. Quote,
build, sign, submit, and poll over four endpoints, all specified in the
API Reference.
Why Geodesics
- Gasless: execution costs come out of the input token. A wallet holding only USDC can still transact anywhere.
- Self-custodial: Geodesics never holds keys or funds. The agent signs and funds move directly from and to its own wallet.
- Any wallet: a raw key, an embedded wallet, or a Virtuals agent wallet. Each onboards itself during its first swap from a chain, gasless, with a one-time signed authorization.
- Keys never stored in plaintext: wallet keys live encrypted in the OS keychain and the API stores only a hash of your API key.
- One API for EVM + Solana: the same quote → build → submit → status loop covers all supported chains, from Ethereum and Base to Robinhood Chain and Solana. Gasless stable withdrawals ride the same rails.
- Machine-first errors: typed error codes like
NEEDS_DELEGATIONandNO_ROUTEtell your agent exactly what to do next.
Start here
Quickstart
From a fresh agent to its first swap in one prompt or five manual steps.
Agent skill
The one-prompt setup, the packaged
SKILL.md, and the agent error playbook.TypeScript SDK
One-call swaps for server-side integrations, typed end to end.
REST API
The raw wire in four requests, plus the interactive API Reference.
