arka: a Rust SDK for AI agents that need to transact on chain

Why a Rust SDK

When agents transition from "demo that talks about tokens" to "process that actually signs transactions and moves money," the failure modes change. Latency stops being an aesthetic preference and becomes the difference between filling and missing an auction. Type safety stops being academic and becomes the difference between a typed-token mismatch failing at compile time and silently approving the wrong contract.

The Python ecosystem (web3.py + LangChain) is great for prototyping but brittle in production. The JavaScript ecosystem (ethers, viem) is excellent for browser wallets but not built for server-side competitive workloads. Every chain ships its own SDK with its own conventions. We kept reaching for a Rust SDK that didn't exist.

What arka gives you

use arka::prelude::*;

let agent = Agent::builder()
    .chain(Chain::Base)
    .wallet(Wallet::generate()?)
    .build()
    .await?;

let tx = agent.dex()
    .swap("ETH", "USDC", parse_ether("0.1")?)
    .slippage_bps(50)
    .execute()
    .await?;

let response = agent.mpp()
    .pay("https://api.example.com/inference", 0.001)
    .await?;

One agent object. Wallet, chain, DEX, oracle, MPP — all unified. No glue, no coordinated upgrade dance across five SDKs.

Status: MVP

Agent, wallet, chain, and tx modules are usable today. DEX, MPP, and oracle modules are in active development. Solana and Cosmos connectors are planned (the Rust ecosystem makes these comparatively easy). See the module status table in the docs.

Why this matters now

Two converging trends make a Rust agent SDK timely. First, intent-based DeFi (ERC-7683) means solvers compete in auctions where milliseconds matter — JS/Python solvers will lose. Second, machine-payments protocols like MPP make it economically interesting for agents to call paid APIs at high frequency, which requires reliable transaction infrastructure that Python can't deliver.

arka is part of the kcolbchain Rust agent stack alongside resolver (intent solver) and arbitrum-cli (chain CLI). Same conventions, same type system, same distribution model.