In many onchain apps, swap route selection is usually determined by the quoted price from their swap providers. 0x's routing engine optimizes for what settles: whether the trade executes at all, and how far the amount that lands drifts from the amount promised. That standard puts the pressure on data. On Solana, a quote is only as good as the account state it was priced against.
In August 2026, 0x brought that discipline to Solana. 0x Swap API on Solana entered open beta, the first non-EVM network informed by more than nine years of onchain trading, and it arrived with users ready to route: Kamino, which uses 0x for swaps inside its lending protocol; Matcha Meta, 0x's own meta-aggregator, which settled millions of dollars in volume during the beta; and Titan, a meta-aggregator that makes providers compete on the settled amount.
What rebuilding the Swap API for Solana meant
On EVM chains, the Swap API returns a transaction, ready to sign. For Solana, 0x chose a different shape: instructions, each one priced against live account state, that the integrator assembles into the transaction it submits. Multi-hop routes are compiled via Address Lookup Tables that are compact enough to fit within Solana's limits. The instruction set creates token accounts as it goes and handles native SOL without a wrap step. Token-2022 routing followed in the July closed beta for stablecoins, tokenized equities, and launchpad tokens. All of it depends on fresh account state, delivered directly through
최신 소식을 받아보세요
최신 엔지니어링 인사이트, 제품 업데이트, 웹3 뉴스를 여러분의 이메일로 바로 받아보세요.
The workload under a Solana quote is not transaction sending. 0x describes it as "essentially account tracking at scale": accounts, subscriptions, and direct RPC fetch keeping pool state current. 0x's API holds around 3,000 active WebSocket connections and ingests more than 100 account updates every second. The fetch path carries as much weight as the subscriptions; 0x calls it critical to the Swap API's low latency on Solana. Solana slot times are getting shorter, from 400ms to 350ms in August 2026, with staged cuts toward 200ms ahead. Every slot can move the pools behind a quote, so the window for a fresh one keeps narrowing. A slow update produces a stale quote. A dropped subscription produces the same thing, without erroring.
0x lists three things the launch depended on: stability under heavy account-update throughput, subscription connections that hold, and low-latency responses under high request load. Behind them sits the bar 0x sets for everything it ships, 99.5% monthly uptime. That reliability is a large part of why teams across chains route through 0x, and the same standard lands on its providers. Supporting it is, 0x says, "non-negotiable."
Standing up Solana: three infrastructure calls
Bringing the Swap API to its first non-EVM network meant three distinct decisions. 0x's Solana team was specific about each.
The first was whether to use a Solana specialist or a multichain provider. 0x cared most about handling high-volume subscription and request data. Some providers can do that on Solana, but in 0x's assessment, "they can only do Solana," which would come at the cost of complicating their RPC vendor stack. On capability, 0x found Quicknode's product "well fleshed out and performant for what we needed." The hardest test was concurrency, supporting that many subscriptions at once. The team called it "a genuinely tough ask, and Quicknode met it." The existing EVM partnership added years of track record and support, and it meant one partner and one package across every product 0x runs, not another Solana-only vendor in the stack.
The second was how much capacity to reserve, and across how many regions. 0x ran its own evaluation. In early testing, the Quicknode Pro network showed one of the lowest p90 latencies among the providers 0x measured. The team then moved to Quicknode Dedicated Clusters: reserved capacity across two regions, with fallback to the Pro network. Latency at p90 fell ~70%.
The third ran counter to the company's instincts. This is a builder-first team, and running its own Solana nodes was weighed, briefly. Two things settled it: cost, and more importantly, expertise. Per the team, "there's a lot about Solana that requires specific expertise." Handing the nodes to Quicknode put 0x's engineers on the one problem only 0x could solve, rebuilding the Swap API for Solana, "which itself was no small task."
Since the open beta
The first signal came without intervention from 0x's team. Individual integrators scaled from tens of requests per second to 200 RPS with no change on 0x's side. 0x credits that growth to the architecture of their API as well as to the RPC provider underneath it.
In July, during the closed beta, 12 to 14 distinct teams a week called the Solana endpoint. In August, 33 a week (2.4x to 2.8x). Teams making their first-ever Solana call went from one a day to three. Latency at 0x's gateway held: p50 around 15ms and p95 around 80ms while the integrator count more than doubled. Over the same July-to-August window, the server error rate fell from 0.19% to 0.017%, an 11x reduction. 503s went to zero.
"What makes Quicknode stand out is their support. The team is responsive, knowledgeable, and easy to get hold of when something needs attention. I'm not waiting a week for a resolution. Underneath that, Quicknode Dedicated Clusters brought our latencies down, which is why we moved in the first place."
Daniel Harris, Solana Engineering Lead, 0x
Quicknode was already a provider for 0x's Swap API on the EVM side. That relationship now also carries the first non-EVM network the API supports, and the account state its Solana quotes are priced against.
