Monero remains one of the most actively used assets in crypto, but acquiring it has changed shape. Spot access has concentrated into fewer venues across a number of jurisdictions in recent years, while on-chain activity for the asset has held steady. The practical result is that for most people, the swap route itself has become the primary way to acquire XMR, rather than an exchange listing.
That makes the design of the swap route worth understanding. Here is how these services actually work, and the three questions that separate one from another.
Why Monero is structurally different
If you have bridged assets between EVM chains, you have a mental model that does not transfer to Monero.
On EVM chains, a bridge is typically a smart contract. Assets get locked on one chain and minted on the other, with rules enforced by code you can read.
Monero has no smart contract layer. It was designed as a privacy-preserving payment system, and that design deliberately excludes the programmability EVM bridging depends on. There is no contract on Monero that can hold XMR and release it according to published rules.
This is why the architecture of a Monero swap route is the whole product. Every service solves the same problem differently, and the differences show up in three places: the price you get, how long settlement takes, and what happens if your transaction gets flagged.
Question 1: How pricing works
Traditional instant swap exchanges operate as market makers. They hold inventory across assets, quote you a single all-in number, and take a spread that is not itemized.
Because there is no visible orderbook, there is nothing to compare the quote against. Analysis of the category has consistently found effective all-in costs of 3% to 4%, against advertised rates often below 1%. The difference is not fraud. It is what happens when one party sets the price and the other has no reference point.
An alternative approach is to route the trade through an actual orderbook. This is the design used by Wagyu.xyz: orders execute against Hyperliquid's onchain orderbook, where professional market makers compete for the fill. The price is a market outcome rather than an operator's decision.
How to verify this yourself: request a quote, then compare the implied rate against XMR spot on a liquid venue. Repeat at several sizes. On a routed model the two track closely and hold shape as size increases, and that consistency is the signature of a real book rather than a managed inventory.
Question 2: How settlement works
The mechanical path for a swap into native Monero on Wagyu.xyz:
Quote. You request an exact-input or exact-output quote through the interface or API.
Order creation. A durable order is created with funding instructions, meaning a deposit address and amount.
Deposit and screening. You send the source asset. Screening runs against the deposit before execution.
Execution. The trade routes through Hyperliquid's orderbook. XMR1, a wrapped representation of Monero on HyperCore, is used in flight.
Settlement. Native XMR is sent to your Monero address. Twenty confirmations are required.
Reported timing is a median of around 5.5 minutes, with the 90th percentile at 13.2 minutes. That is a tight distribution, which is the more useful signal. A median tells you the typical case. The gap between median and 90th percentile tells you how predictable the service is.
Question 3: What happens if you get flagged
This is where design differences become consequential, and it is the part most users do not think about until it happens to them.
The standard industry pattern is post-hoc screening. The service accepts your deposit, then screens. Roughly 2% to 5% of transactions get flagged. At that point, a service that marketed itself on requiring no identity will request one, meaning passport, proof of address and source of funds, as a condition of returning your money.
The issue is not that screening exists. Every operator has legal obligations. The issue is sequence. Once a service holds your deposit and has flagged it, the incentives break: the operator controls both the asset and the timeline, and resolving your case quickly has no upside for them.
Pre-execution screening inverts this. Wagyu.xyz screens the deposit before executing the swap, and deposits that do not pass are returned to the originating address. Because the rejection happens at the boundary, the operator never reaches the state of holding contested funds indefinitely. The compliance policy published at docs.wagyu.xyz states it does not request KYC documentation, and applies asset restrictions only under a valid court order from a competent authority.
Building your own swap service on Wagyu.xyz
One development worth understanding, whether you are a user or a builder: the infrastructure behind Wagyu.xyz is publicly available.
The API documented at docs.wagyu.xyz covers the full lifecycle, meaning asset discovery, quoting, order creation and tracking. The components that historically made an instant swap exchange hard to launch are now something you call rather than something you build:
Liquidity relationships and market makers. Now an HTTP request.
Treasury and inventory management. Not required, because you hold nothing.
Monero bridge infrastructure. Handled upstream.
Compliance screening tooling. Applied before execution upstream.
Spread risk management. Not required, because you set margin on a routed rate.
The documented flow follows four steps. Discover available assets and bridge status, reading asset decimals from the response, since atomic amounts are strings and floating-point values should not be used. Quote routes for exact-input or exact-output amounts. Create a durable order with funding instructions. Track order state over REST, with WebSocket for real-time updates.
Your margin sits on top of the routed rate. If Wagyu.xyz returns a quote and you present the user a slightly different number, the difference is your revenue, and you never take inventory positions to earn it.
When the API launched, the founder's own suggested approach was to hand the documentation to an AI coding assistant and build from there. That is a reasonable description of the workload. A documented REST API with a four-step flow and a generated OpenAPI contract is close to the ideal case for AI-assisted development, and a developer with a modern coding assistant can realistically go from documentation to working swap front-end in an afternoon, because the hard problems are all upstream.
Builders have used this to launch wallet integrations, regional interfaces and community-branded swap services. If you maintain a wallet, a privacy tool, or a community with recurring XMR demand, running your own swap service is now a weekend project rather than a funding round.
Two implementation notes: the API covers public integrations, so treasury, recovery and operator controls are not exposed. And the generated OpenAPI and AsyncAPI contracts from the engine take precedence over the prose documentation, so build against the contracts.
The bigger picture
For most of Monero's history, the on-ramp layer was opaque by default, with prices set unilaterally, screening applied after the fact, and no reference market to check anything against. Moving execution onto a public orderbook makes the price contestable and the process legible. Opening the infrastructure so anyone can compete on top of it accelerates the same effect.
Wagyu.xyz reports more than $700 million in cumulative volume since its January 2026 launch, it has quickly grown into the largest XMR exchange.