Can institutions use XRPL AMMs through Ripple's APIs?

The full answer

What do Ripple’s AMM APIs do?

Ripple’s Wallet-as-a-Service documentation carries a changelog entry on the XRP Ledger AMM APIs. Its security considerations state that transactions initiated using the AMM APIs are subject to the same policy engine rules, and that because AMMCreate and AMMDeposit withdraw multiple assets from the wallet, the policy engine expects policies to be defined for each affected asset [1]. The entry covers three XRP Ledger transaction types: AMM Create, AMM Deposit and AMM Withdraw [1]. A withdrawal redeems LP tokens either for both pool assets or for the first asset only [1].

The pools are part of the ledger itself. Ripple’s Q1 2024 XRP Markets Report says the XLS-30 amendment went live on mainnet and added a non-custodial automated market maker as a native feature of the ledger’s decentralized exchange [2]. The API gives Ripple’s wallet customers a programmatic route into those same pools. How the pools price trades and share fees is explained in how XRP Ledger AMMs work.

Ripple lists two use cases [1]. Both are Ripple’s descriptions of its own product. Neither comes with a measured result.

What stage are the APIs at?

Ripple’s changelog categorizes the APIs as “Alpha (unstable API, expect changes)” [1]. The headline says “live”, and the category label says Ripple may still change the interface.

Ripple lists these limits on the same page [1]:

• The AMM APIs work on the XRP Ledger only.
• AMM Deposit is supported only in two-asset mode. A single-asset deposit into a two-asset pool is unsupported.
• The lpTokenOut request parameter is not yet supported.

What controls sit around these transactions?

Ripple says transactions sent through the AMM APIs follow the same policy engine rules as other wallet transactions [1]. AMM Create and AMM Deposit take more than one asset out of the wallet, so the policy engine expects a policy for each affected asset. For issued assets, the policy must also define the issuer [1]. The wider Wallet-as-a-Service documentation has sections on MPC-TSS, policies, the Travel Rule, and transaction freeze and compliance controls [1]. The custody arrangements behind these wallets are covered in what Ripple Custody is and which banks use it.

The AMM changelog does not say whether institutions can limit pools to verified counterparties. At the ledger level, Messari’s Q1 2026 report, as reported by crypto.news, says Permissioned Domains and the Permissioned DEX went live on XRPL that quarter [5]. Those tools are covered in the XRP Ledger’s compliance features for institutions.

Which institutions are using the APIs in the alpha?

Ripple’s changelog names no customers [1]. As of September 30, 2026, I could not find any source naming a firm that uses the AMM APIs. Ripple’s documentation calls the users “customers” and does not define who is eligible.

When is general availability expected, and what is the dated record so far?

The dated record:

• Q1 2024: Ripple’s markets report says XLS-30 went live on mainnet, adding the native AMM. The report says community members found a bug affecting the AMM shortly after launch, and a fix was on mainnet as of April 11 [2].
• Q1 2026: Messari, as reported by crypto.news, says Permissioned Domains and the Permissioned DEX went live on XRPL [5].
• March 13, 2026: CoinDesk counted 27,000 AMM pools holding 12 million XRP [3].
• Read September 30, 2026: Ripple’s changelog lists the AMM APIs as live and categorized Alpha [1].

Has pool depth changed since the APIs went live?

Pool depth before and after the APIs cannot be compared, because Ripple has not published a release date. The closest dated measure comes from Evernorth, which The Crypto Basic describes as the largest XRP treasury firm by holdings. Evernorth’s report, as reported by The Crypto Basic on September 3, 2026, says that over the six quarters to Q2 2026 XRP-paired pools grew 26% while trading through those pools fell 74% [4]. Evernorth holds XRP, so it has an interest in the network. Other pool-size figures, and why they differ, are in how much liquidity is in XRPL AMMs.

What risks does a liquidity provider take on?

Two risks come straight from the sources. The interface is Alpha and may change [1]. The AMM feature itself had a bug shortly after its 2024 launch, which was fixed on mainnet as of April 11 [2]. Wider risks of putting XRP into pools are covered in the risks of earning yield through AMM pools or wrapped XRP.

What does the skeptical case say?

CoinDesk wrote on March 13, 2026 that AMM pool growth is real, but the dollar value of that liquidity remains thin relative to the scale of the token’s market [3]. A crypto.news analysis of Ripple’s product stack says skeptics do not deny the infrastructure is real. They deny that infrastructure owned by the token’s issuer counts as token demand when third parties have not adopted it. The publication concludes that “on the evidence to date they have been right” [7]. That argument applies to a Ripple-built API as much as to Ripple’s other products. The wider version of this critique is on whether money is going into XRP infrastructure ahead of real demand.

Why would an API matter if the pools already exist?

In its Ripple Mint post of July 23, 2026, Ripple wrote that manual workflows do not fully support institutions operating at scale, where automation, real-time visibility and system integration are critical [6]. That post was about stablecoin access and workflows for institutions. The AMM APIs follow the same approach for pools that have been on the ledger since Q1 2024 [2]. On Ripple’s own framing, the obstacle for firms was plugging pools into policy-controlled wallet systems, not whether pools existed. An API does not add liquidity on its own. It changes the pools only if customers deposit through it, and no source the project holds measures that. Whether announcements like this one turn into used products is tracked in whether XRPL institutional announcements are becoming live products.