Table of Contents
Altair RLUSD settlement puts daily AI model-token invoices on the XRP Ledger: Altair joined XRPL AI Hub as an x402 merchant, and payers can settle those invoices in RLUSD through t54's XRPL facilitator (t54).
The announcement landed on 4 November 2026, but Altair's merchant profile already lists an October 24 join date and live RLUSD volume (Blockster; XRPL AI Hub). Model requests still go through Altair's API; the onchain step is the daily invoice, not every token call (t54).
This guide explains how Altair RLUSD invoice settlement works, what the hub shows for payments and volume, how daily RLUSD batching compares with per-request USDC x402, where vendor claims leave gaps, and what operators should verify before automating payment.
Key Takeaways
- Altair is an active XRPL AI Hub x402 merchant with a resource called Altair Daily Invoice Settlement that accepts variable RLUSD pricing (t54, XRPL AI Hub).
- As of 4 November the hub showed 47 payments and 12,425.94 RLUSD volume; by the morning of 5 November those totals were 51 payments and 14,391.34 RLUSD (Blockster; XRPL AI Hub).
- A recorded invoice payment incurred an XRPL network fee of 10 drops (0.00001 XRP), so ledger cost at the invoice level is effectively negligible (t54, Blockster).
- Claw Credit-backed agents that auto-pay each customer's daily invoice remain planned integration work, not a live Altair customer feature (t54).
- Daily RLUSD batching wins on fee count versus per-request USDC x402 when an agent makes many model calls a day; the trade-off is credit risk during the day and a variable invoice amount (Stablecoin Insider analysis).
What is Altair RLUSD invoice settlement?
Altair RLUSD invoice settlement is an x402 resource that lets an agent or payer settle an existing Altair daily invoice in RLUSD on XRPL, with verification and settlement handled by t54's facilitator (t54). Altair meters model-token consumption for business customers and produces usage-based daily statements; the integration connects that billing workflow to XRPL at the invoice level rather than per model call (t54).
Altair's own site frames the company as credit infrastructure for enterprise AI, selected for the Brinc x Ripple Hong Kong Financial Innovation Program 2026 cohort, with XRPL-based settlement still described as under development on the homepage (Altair). The live x402 merchant path is separate and already listed on XRPL AI Hub (XRPL AI Hub).
| Item | What is published | Source |
|---|---|---|
| Announcement | 4 November 2026: Altair joins XRPL AI Hub as an x402 merchant for daily RLUSD invoice settlement | t54; Blockster |
| Merchant join date | 24 October 2026 | XRPL AI Hub; Blockster |
| Resource | Altair Daily Invoice Settlement; price varies; asset RLUSD | XRPL AI Hub |
| Settlement URL pattern | https://x402-settlement.altair.credit/x402/invoices/{invoice_id} | XRPL AI Hub |
| Merchant address | rBy7V2qW93u2P7cUTkMAvP7zF6daKKcMid | XRPL AI Hub |
| Facilitator | t54 XRPL x402 facilitator (hosted mainnet) | xrpl-x402.t54.ai |
| Network fee example | 10 drops (0.00001 XRP) on a recorded invoice payment | t54; Blockster |
| Next step (planned) | Claw Credit agents mapped to Altair customers for automated daily payments | t54 |
How does an Altair AI bill become an RLUSD payment?
The customer keeps calling models through Altair's API; Altair meters usage into a daily invoice; an agent or payer then requests that invoice's x402 resource, receives RLUSD payment terms, and pays Altair's merchant address, with t54 verifying and settling the payment (t54; Blockster).
Blockster summarized the loop in four steps that match the vendor write-up:
| Step | What happens |
|---|---|
| 1. Use AI models | The customer sends requests through Altair's API. |
| 2. Calculate the bill | Altair meters usage and creates a daily customer invoice. |
| 3. Retrieve payment terms | An agent or payer accesses that invoice through the x402 resource. |
| 4. Settle in RLUSD | Payment goes to Altair's merchant address; t54 verifies and settles. |
Steps paraphrased from Blockster and t54, read 5 November 2026.
Under the hood this is the XRPL exact scheme: the payer signs a standard XRPL Payment, the facilitator submits the presigned blob, and the invoice is bound via Memos or InvoiceID so the same payment cannot be replayed against another invoice (t54 XRPL scheme docs). For RLUSD, the asset field uses the canonical 40-hex currency code and the issuer sits in extra.issuer (t54 XRPL scheme docs).
Stablecoin Insider previously covered how t54 pairs Verifiable Intent with XRPL agent payments in its XRPL Mastercard Verifiable Intent write-up, and compared facilitators more broadly in best x402 facilitators compared.
What do the live Altair merchant totals show?
They show a small but growing RLUSD invoice book, not a disclosed customer count. Blockster, checking on 4 November, reported 47 payments received and 12,425.94 RLUSD in total volume on the Altair merchant profile (Blockster). Stablecoin Insider re-read the same hub page on the morning of 5 November and found 51 payments and 14,391.34 RLUSD total volume, with one active API and the October 24 join date unchanged (XRPL AI Hub).
| As of | Payments received | Total volume (RLUSD) | Source |
|---|---|---|---|
| 4 November 2026 (Blockster check) | 47 | 12,425.94 | Blockster |
| 5 November 2026 morning (SCI re-read) | 51 | 14,391.34 | XRPL AI Hub |
| Join date | 24 October 2026 | n/a | XRPL AI Hub |
| Active APIs | 1 | Altair Daily Invoice Settlement | XRPL AI Hub |
Hub totals are merchant-level, not a count of distinct customers (Blockster).
Recent hub rows also show how uneven daily invoices can be. On the first page of recent payments, individual RLUSD values included amounts such as about 1,700.54, 1,504.83, 1,391.92, 222.54 and several sub-3 RLUSD settlements, all marked against the same buyer address prefix (XRPL AI Hub). That pattern fits invoice batching better than a flat per-call price list.
The network fee story is separate from the AI bill. t54 and Blockster both highlight a publicly recorded Altair RLUSD invoice payment that cost 10 drops, or 0.00001 XRP, in XRPL network fees (t54; Blockster). That figure is the ledger fee, not the price of the AI service.
How does daily RLUSD batching compare with per-request USDC x402?
Daily RLUSD invoice batching wins on payment count and ledger fees whenever an agent makes many model calls a day, because Altair settles once per invoice instead of once per request (t54). Per-request USDC x402, the pattern used by many Base sellers, still wins when you need instant release of a single paid resource and a known unit price.
Stablecoin Insider's worked example uses published rails, not Altair's undisclosed model rates. Assume an agent makes 5,000 successful model calls in a day. On a per-request x402 rail you would settle 5,000 times; on Altair's daily invoice you settle once in RLUSD (t54). If each Base USDC x402 settlement cost even $0.01 in combined facilitator and gas overhead, 5,000 settlements would be about $50 of payment overhead before the AI bill itself. One XRPL invoice at 0.00001 XRP of network fee is negligible by comparison (t54).
| Dimension | Per-request USDC x402 (typical Base pattern) | Altair daily RLUSD invoice (XRPL) |
|---|---|---|
| When money moves | Every successful paid request | Once per daily invoice |
| Asset | Usually USDC on Base or Solana | RLUSD on XRPL |
| Unit price visibility | Often fixed in the 402 response ($0.01 to $0.25 on public sellers) | Variable; amount equals that day's invoice |
| Payment count at 5,000 calls/day | 5,000 | 1 |
| Ledger fee example | Chain gas + facilitator fee per call | 10 drops (0.00001 XRP) on a recorded invoice (t54) |
| Credit / float risk | Low: pay as you consume | Higher: usage accrues before settlement |
| Best fit | Micropayments for discrete API calls | Business AI bills that already invoice daily |
Comparison is Stablecoin Insider analysis. Altair model rates are not published on the merchant profile (XRPL AI Hub). Public per-call USDC examples include Dataline at $0.25 and CoinGecko at $0.01 (Dataline x402, prior SCI reporting).
Break-even is mostly about overhead and risk, not the AI rate. If your AI bill is $B per day and per-request payment overhead is $F per call across N calls, daily batching saves roughly N times F in payment overhead, at the cost of carrying up to $B of unsettled usage and accepting a variable invoice (t54). For N = 5,000 and F = $0.01, that is about $50 of overhead avoided per day, or about $1,500 per 30-day month, before any difference in the AI rate itself.
Operators who already hold RLUSD can mint and redeem through Ripple's documented flow; Stablecoin Insider walked through that path in how to mint and redeem RLUSD with Ripple Mint. Teams comparing other agent payment products can also read MoonPay PayBox and Atom x402 for adjacent rails.
What does the planned Claw Credit step change?
It would let credit-backed agents pay each mapped Altair customer's daily invoice automatically, but that customer-level automation is still planned work (t54). Claw Credit itself is live as a Trustline-powered credit line for OpenClaw agents that buy x402 services, with supported rails that include Base USDC, Solana USDC and XRPL RLUSD (t54 Claw Credit docs; claw.credit).
The product boundary matters for treasury teams. Claw Credit is a credit facility with registration, underwriting, repayment and suspension, not a simple prepaid wallet (t54 Claw Credit docs). Blockster separately notes that retrieving an invoice and settling a payment are only part of the process; an agent also needs authority to spend for the customer it represents (Blockster).
Where vendor claims leave gaps
Several important numbers are still missing from the public pages. Altair has not published a model-token rate card on the merchant profile, only variable RLUSD pricing for the daily invoice resource (XRPL AI Hub). The hub's payment and volume totals are merchant aggregates, not a disclosed count of customers (Blockster).
There is also a framing gap between sources. t54 describes Altair as an AI model router with usage-based billing (t54), while altair.credit leads with enterprise AI credit, a Master Vault design and HFIP selection, and says production settlement remains subject to deployment on the homepage (Altair). Both can be true for different product lines, but buyers should confirm which contract they are on before pointing an agent at the settlement URL.
Finally, the 10-drop fee example proves ledger cheapness for one payment; it does not prove that facilitator fees, credit fees or FX between USDC and RLUSD are zero (Blockster). Check the live PAYMENT-REQUIRED payload and your own treasury path before you scale.
Who should use Altair RLUSD settlement?
It fits businesses that already buy AI models through Altair (or a similar daily-invoice router) and want those invoices payable in RLUSD by an agent or treasury wallet on XRPL (t54). It fits less well if you need a public per-call price, instant per-request release, or USDC on Base as the only treasury asset.
Before any agent spends, run this checklist:
- Confirm the invoice ID and RLUSD amount in the live 402 response match your own Altair statement.
- Set a hard per-invoice and per-day ceiling in code, separate from any prompt-level budget.
- Verify payTo equals the published merchant address rBy7V2qW93u2P7cUTkMAvP7zF6daKKcMid (XRPL AI Hub).
- Require invoice binding (Memo or InvoiceID) so payments cannot be replayed (t54 scheme docs).
- Keep Claw Credit automation off until spend authority, repayment and suspension rules are written down.
- Decide how you source RLUSD (mint/redeem, exchange or existing balance) before the first settlement.
For a wider view of agent payment design choices, see stablecoin payments for AI agents and how to price an API for AI agents.
FAQ
What is Altair RLUSD?
In this context it is Altair's x402 daily invoice settlement resource on XRPL AI Hub, which accepts variable RLUSD payments for AI model-token invoices (t54, XRPL AI Hub).
When was Altair RLUSD announced?
t54 and Blockster published the announcement on 4 November 2026; the merchant profile lists a 24 October 2026 join date (t54, Blockster, XRPL AI Hub).
How much RLUSD volume has Altair taken?
Blockster reported 12,425.94 RLUSD across 47 payments on 4 November; the hub showed 14,391.34 RLUSD across 51 payments on the morning of 5 November (Blockster, XRPL AI Hub).
What is the XRPL network fee for an Altair invoice payment?
Is Claw Credit already paying Altair invoices?
No. Connecting Claw Credit agents to individual Altair customers for automated daily payments remains planned integration work (t54).
Which facilitator settles Altair RLUSD payments?
t54's XRPL x402 facilitator verifies and settles payer-signed payments; the hosted mainnet facilitator is documented at xrpl-x402.t54.ai (t54 facilitator, t54).
Does Altair publish a per-token price?
Not on the merchant profile. The resource is listed as variable RLUSD pricing tied to each daily invoice (XRPL AI Hub).
What to watch next
Watch for three things: whether Claw Credit automation for Altair customers goes live with public spend limits, whether Altair publishes a rate card beside the variable invoice resource, and whether hub volume keeps rising without a matching disclosure of customer count.
If your team already invoices AI usage daily and holds or can source RLUSD, the settlement path is worth a capped pilot against one known invoice. If you need per-call micropayments with a posted unit price, stay on the public USDC x402 sellers until Altair publishes those terms.
Building agent payment rails yourself? Read the Stablecoin Insider guide to pricing an API for AI agent customers.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal or tax advice. Merchant totals, fees and product status can change; figures quoted here were read on 4 and 5 November 2026 from the cited pages, and the cost scenarios are Stablecoin Insider's own calculations, not tests of the live Altair settlement API. It is not a recommendation to buy or sell any token, including RLUSD or XRP, and no material herein should be interpreted as an endorsement or solicitation.
