Skip to main content
Solana has no delegation step; the agent signs the actual origin transaction. The loop is the same four steps with a different build/submit pair:

Quoting from Solana

Two field-level differences in POST /swap/quote:
  • walletAddress is the agent’s base58 Solana address.
  • recipient is required: the destination-chain address the output is delivered to (there’s no cross-chain default from a Solana wallet to an EVM address).
Solana chain id in this API: 792703809.

Build and sign

POST /swap/build-solana-tx unseals the quote and returns a base64-encoded unsigned v0 VersionedTransaction:
Deserialize, sign with the agent keypair, and re-serialize:
Submit it:
The server broadcasts the transaction and tracks settlement; poll GET /swap/status/:swapId as usual.

SOL top-up gate (same-chain swaps only)

Cross-chain Solana-origin swaps are gasless: the wallet needs no SOL at all, and the origin transaction’s network fees are covered for it. A same-chain Solana swap is the exception; it needs a small SOL balance for the network fee, and below 0.005 SOL (5,000,000 lamports) quoting one is gated:
The fix is to land a small amount of SOL in the wallet; swapping roughly 1.5 USDC → SOL covers it comfortably. That top-up can itself be a Geodesics swap into Solana (e.g. USDC on Base → SOL), since swaps delivering to Solana don’t require SOL either.

Delivering to Solana

Nothing special: any EVM-origin swap can name a Solana outputToken/destinationChain and a base58 recipient. The delegation model on the origin chain applies as normal; see Gasless delegation.