An agent pays $0.10 to resolve a customer escalation.

This is a real HTTP endpoint gated by the x402 protocol. AI agents can pay in USDC on Base, or in XRP or RLUSD (Ripple USD) on the XRP Ledger, and receive a machine-readable response — no accounts, no API keys, no prior relationship. Emerge Digital builds this layer for Gulf enterprises on Cloudflare.

1 — Call it without paying

Any un-paid request receives an HTTP 402 with payment terms an agent can read.

curl -i https://agent-commerce.emergedigital.com/api/resolve-escalation

Response: HTTP/1.1 402 Payment Required + JSON body with the accepted price, network, and receiving address. This is the machine-readable payment offer.

2 — Call it with payment

An agent using the @x402/fetch SDK signs and pays automatically. On Base Sepolia testnet, funds are free — request test USDC from Circle's faucet.

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
// ...register EVM scheme with a test signer
const paidFetch = wrapFetchWithPayment(fetch, client);
const res = await paidFetch(
  "https://agent-commerce.emergedigital.com/api/resolve-escalation"
);
const data = await res.json();
// { ok: true, escalation: { id, resolution_summary, ... }, meta: {...} }

3 — Pay on the XRP Ledger

The same pattern settles on XRPL mainnet: the x402 exact scheme for XRPL was merged into the x402 Foundation spec on 3 July 2026, with settlement through t54 Labs' keyless facilitator. This endpoint quotes 0.01 XRP or 0.0111 RLUSD per call — every 402 on this origin offers both settlement assets and the agent picks one.

curl -i https://agent-commerce.emergedigital.com/api/xrpl/resolve-escalation

Response: HTTP/1.1 402 Payment Required + a PAYMENT-REQUIRED header quoting network: xrpl:0. An agent using the x402-xrpl SDK pays and retries automatically:

import { x402Fetch } from "x402-xrpl";
import { Wallet } from "xrpl";
const paidFetch = x402Fetch({ wallet: Wallet.fromSeed(seed), network: "xrpl:0" });
const res = await paidFetch(
  "https://agent-commerce.emergedigital.com/api/xrpl/resolve-escalation"
);
// settled on-ledger; receipt in the PAYMENT-RESPONSE header

Service metadata for indexers is published at /.well-known/x402.

Vela OS products — API editions

Five products from the Vela OS line are purchasable per call over x402: Vela AEO (answer-engine optimization), Vela Assist (a governed assistant exchange), Vela Recs (embedding-based recommendation ranking), Vela Commerce (commerce feed validation and markup), and Vela Scan (agent-readiness scan of a URL). Each call delivers the artifact its listing describes — the per-call API edition of the product line — and usage is metered in Metronome. LLM-generated portions are labeled in every response. Like the rest of the catalog, each 402 offers two settlement options — XRP or RLUSD — with the Vela OS products anchoring RLUSD at exact USD parity with the product rate card (the XRP leg approximates USD at the on-ledger rate).

The full catalog

Every resource below answers with HTTP 402 and machine-readable terms; agents pay per call in XRP or RLUSD on the XRP Ledger. Loaded live from /api/catalog; discovery document at /.well-known/x402.

Why this matters

Cloudflare launched the Monetization Gateway on 1 July 2026 to charge AI agents for any resource behind Cloudflare — web pages, datasets, APIs, or MCP tools. Coinbase and Cloudflare co-founded the x402 Foundation. The protocol is real, the volume is real (over 165M transactions to April 2026), and Gulf enterprises procuring Agentforce and Copilot programmes this year will need this layer.

Emerge Digital is the local Cloudflare-native prime that builds it — no wallet infrastructure to run, no on-chain code your compliance team has to reason about.