Built on Fogo Chain L1
Argyros API: Operational
Get API Key →
Built on Fogo Chain L1
Argyros searches every liquidity pool on Fogo's native SVM, splits your order for the best fill, and hands back a ready-to-sign transaction. One HTTP call. No RPC round-trips.
40ms finality, sub-cent fees, deterministic ordering. The chain does the hard part — we route on top of it and stay out of the way.
We didn't pick Fogo for the narrative. We picked it because the numbers hold up.
Five stages, ~125µs at p50. Each one runs in SVM memory — no serialization tax between them, no network hops back to an RPC.
Every endpoint, no rate caps, no card. Grab a key in Discord and tell us where it breaks.
Most aggregators talk to a chain over RPC. Argyros is compiled for the SVM and scheduled alongside validators, so it reads pool state straight from the ledger. There's no RPC hop sitting between you and the current price.
Routes are assembled in SVM memory and handed back as a serialized transaction your signer can use as-is — no intermediate buffers, no re-encoding step. That's where the sub-millisecond number actually comes from.
The same routing engine, wrapped in a swap UI your users can sign with. It's a plain Web Component — works in React, Vue, Svelte, or hand-written HTML — and themes to your brand with a handful of CSS variables. The card on the right is the real thing.
<!-- one script, one element --> <script src="https://cdn.argyros.trade/argyros-widget.umd.js"></script> <argyros-swap api-key="argy_live_xxx" chain="fogo" theme="dark"></argyros-swap>
Demo embed · add a publishable key + your API endpoint to go live
“We benchmarked every aggregator on Fogo. Argyros was the only one that stayed under a millisecond at size. For a market-making desk, that's not a feature — it's the whole strategy.”
Not here? The people who wrote the engine answer in #argyros-dev on Discord — usually within the hour.
Authorization: Bearer $ARGYROS_KEY to every request. API keys are issued per-project from the dashboard; rate limits scale with your tier.
slippageBps on the quote request. The minimum-out check is compiled into the route plan itself and enforced on-chain — if the route can't deliver, the transaction reverts atomically. No partial fills.
wss://api.argyros.xyz/api/v1/stream pushes fresh quotes on every pool-state update — typically 200–400 ticks/second per pair. Subscribe to as many pairs as your tier allows.
One endpoint, one signature. Built for the people who notice when execution is measured in microseconds instead of seconds.