Your AI Coding Agent Can Now Query SODAX Live Data — Here's How

Source: Dev.to

Overview

So I’ve been playing around with the SODAX Builder MCP server this week, and honestly it’s one of those things that seems small until you actually use it.

If you’re building cross‑network DeFi tooling and you’re tired of tabbing out to check docs mid‑session, this is for you.

SODAX published a Builder MCP endpoint (https://builders.sodax.com/mcp) that plugs directly into Claude, Cursor, Windsurf, or anything else that speaks MCP. Your agent gets live protocol data—not cached, not from training, but the actual current state of the network.

Quick primer on MCP (if you’re not familiar)

Model Context Protocol is an open standard for giving AI assistants access to external tools at runtime. Instead of your agent guessing which tokens are supported or which networks are live, it just… asks. The SODAX builder endpoint answers.

Add https://builders.sodax.com/mcp to your agent config and you’re done.

What’s actually in the Builder MCP?

Here’s what you get:

• sodax_get_supported_chains – pulls the full list of networks SODAX runs on. Currently 17: Ethereum, Arbitrum, Base, Optimism, Polygon, Avalanche, BNB Chain, Sonic (the hub), HyperEVM, LightLink, ICON, Solana, Stellar, Sui, Kaia, and a couple more.
• sodax_get_swap_tokens – returns tokens available for swapping, filterable by network. Super useful before writing integration code.
• sodax_get_money_market_assets – the 20 assets in the money market for lending and borrowing.
• sodax_get_orderbook – live open intents sitting in the solver queue.
• sodax_get_transaction – look up any transaction by hash. Genuinely handy mid‑debug.
• sodax_get_user_transactions – history for a given wallet.
• sodax_get_user_position – a wallet’s current borrow/lend position in the money market.
• sodax_get_volume – solver volume data with filtering.
• docs_searchDocumentation – searches the SODAX SDK docs directly. This one I use constantly.

Why it’s actually useful (not just cool)

Building with SODAX means working with an execution coordination system spanning 17 networks. The Solver picks execution paths, the Coordinator monitors the plan, the Liquidity layer treats assets as one unified pool, and sodaVariants extend assets into networks where they don’t natively exist.

That’s a lot of moving parts to keep track of. Having your agent pull the current state instead of guessing cuts a real amount of friction.

The @sodax/sdk handles swaps, lend/borrow, bridging, staking, and the ICX‑to‑SODA migration flow. The wallet‑connection layer (@sodax/wallet-sdk-core and @sodax/wallet-sdk-react) covers EVM, SVM, and non‑EVM environments. MCP connects it all to your agent at runtime.

Concrete situations where this saves time

• Integration work – Ask your agent to fetch supported swap tokens for a specific network before writing any code. No context‑switching.
• Debugging – Drop a transaction hash and ask your agent to check execution status. No leaving the editor.
• Writing docs or content – Pull a canonical definition from the SODAX glossary or grab recent news article URLs without hunting them down manually.

A bit of context on the protocol itself

SODAX isn’t a bridge and it isn’t a messaging standard. It’s an execution‑coordination layer. The difference matters because bridges move assets; SODAX coordinates outcomes, handling:

• Liquidity fragmentation
• Asynchronous execution
• Recoverability
• State transitions

…in ways that raw bridging doesn’t.

Fourteen partners are already live on it, including Hana Wallet, Houdini Swap, Amped Finance, and Balanced.

The SODA token handles governance, with a fixed max supply of 1.5 B. If you’re coming from ICX, migration is 1:1.

Happy building!

Protocol fees go toward the DAO, staking rewards, burns, and POL growth.

Worth bookmarking: there’s a dedicated AI Agents concept page that’s directly relevant if you’re thinking about agentic DeFi workflows—exactly what the MCP server opens up.

What’s shipped recently

• SODAX is live on Kaia – swap access extended to the Kaia community, now 17 networks total.
• Solver v3 dropped in February – rebuilt for more resilient cross‑network execution.
• March update – unifying cross‑network liquidity and opening up SODAX Save for yield.
• CEX migration support is live, so ICX‑to‑SODA conversion happens automatically on supported platforms.

Getting started

• Builder MCP endpoint: https://builders.sodax.com/mcp
• Add it to your agent and start querying.
• For SDK integration, the best starting points are docs.sodax.com or the integration guide on the SODAX site.

If you have questions, head over to Discord.