Skip to main content
Live demos: every app below runs against the XentFi sandbox. No account needed — click into any one and try the flow yourself.
Each demo below is a small, fictional company built to show one XentFi capability end to end — the same UI a real merchant or developer would ship, wired to the same integration code shown in each demo’s Build it yourself section. Together they cover the full surface: an autonomous agent with its own wallet and policy, automatic currency conversion on receipt, per-invoice deposit addresses, machine-to-machine payments over x402, and a hosted checkout page.
Grid of all five XentFi demo apps — Aria, CreatorPay, InvoiceFlow, ModelMesh, and Nova Threads

What you can test


Aria — agent wallets & spending policies

Aria demo: a procurement agent submitting a purchase request, evaluated against a monthly budget and vendor allowlist in real time
Aria is a procurement agent with her own XentFi Agent Wallet and a spending policy her (fictional) finance team set once — a monthly budget, a per-transaction cap, and a vendor allowlist. She renews SaaS subscriptions autonomously, and every payment she attempts is checked against that policy server-side before a single token moves. On the demo, pick a vendor and an amount and submit a purchase request — you’ll watch Aria check the request against her live policy, sign with her agent wallet, and broadcast on-chain, or get denied with the specific reason (off-allowlist vendor, over the per-transaction cap, or over budget for the month). How it works:
1

Create the agent and its wallet

Register an Agent identity, then delegate it a chain-scoped wallet it can transact from — separate from the main treasury.
2

Attach a spending policy

Set per-transaction and monthly USD limits plus a vendor/recipient allowlist. This is what runs on every purchase request submitted in the demo.
3

Agent calls the Agent Payments API

Aria’s own scoped API key calls the payments endpoint directly — no backend has to broker each individual purchase.
4

React to the outcome

Approved payments return a transaction hash immediately. Denied ones return a machine-readable reason the agent (or a human) can act on.

Visit the demo

demos.xentfi.com/aria

Build it yourself

Agent Tools guide, plus the Agent tab’s Quickstart and Tools Reference

CreatorPay — auto-settlement

CreatorPay demo: an incoming tip in ETH, MATIC, or ARB converting to USDC in real time via an auto-settlement rule
Fans tip creators in whatever they’re holding — ETH, MATIC, ARB. CreatorPay’s auto-settlement rule converts it to USDC the moment it arrives, so creators never carry volatile exposure they didn’t ask for. Pick a source asset and amount and simulate an incoming tip — you’ll watch the rule trigger, find a route under the configured slippage tolerance, execute the swap, and credit USDC to the payout wallet. How it works:
1

Create an auto-settlement rule

Define which incoming assets should trigger conversion, a single destination asset and wallet, and the route strategy to use.
2

Funds arrive at a watched wallet or address

Any tip in an accepted source asset landing on that wallet is picked up automatically — nothing to poll.
3

The rule engine finds a route and executes

Based on the chosen strategy (fastest, cheapest, recommended, or no-slippage) the conversion executes within the configured slippage tolerance.
4

React to the settlement webhook

A settlement.executed webhook fires with the source amount, destination amount, and route used — that’s what populates the log on the demo.

Visit the demo

demos.xentfi.com/creatorpay

Build it yourself

Liquidity & Settlement guide

InvoiceFlow — deposit addresses

InvoiceFlow demo: a list of client invoices, each with its own dedicated USDC deposit address and payment status
Every invoice on InvoiceFlow gets its own dedicated deposit address — no shared wallet, no memo codes to get wrong. Create an invoice and you’re issued a fresh address scoped to that client and amount; simulate the client’s payment and watch the invoice reconcile automatically. How it works:
1

Create a deposit address per invoice

When an invoice is issued, request a fresh deposit address scoped to that invoice — never reuse one address across clients or invoices.
2

Show the client where to pay

Display the address (and a QR code) alongside the amount and asset expected — the client sends funds directly, no intermediary custody step.
3

Listen for the deposit webhook

XentFi watches the address on-chain and fires a webhook the moment funds land — no polling a block explorer.
4

Reconcile automatically

Match the webhook’s addressId back to the invoice record and flip its status — exactly what the demo’s “Simulate client payment” button does.

Visit the demo

demos.xentfi.com/invoiceflow

Build it yourself

Addresses guide

ModelMesh — x402 facilitator

ModelMesh demo: an AI agent calling a pay-per-call API, receiving a 402 Payment Required response, and completing payment via the XentFi facilitator
ModelMesh is a marketplace of pay-per-call model APIs — an image upscaler, a sentiment analyzer, a text-to-speech endpoint. No API keys, no monthly plans: an agent hits an endpoint, gets a 402, pays in one round trip through the XentFi Agent Facilitator, and the request completes. Click Call on any API and watch the full round trip play out live — the demo’s /verify and /settle steps are real calls to the facilitator, not just an animation, and the flow ends with the actual API response. How it works:
1

Return 402 with payment requirements

The resource server responds with HTTP 402 and a JSON body describing the price, asset, network, and payout address for the requested resource.
2

Agent attaches a payment payload

The calling agent’s wallet signs a payment authorization and retries the request with an X-PAYMENT header — no separate checkout flow.
3

Verify with the facilitator

The resource server calls the facilitator’s /verify endpoint to confirm the payment payload is well-formed and the agent can cover it, before doing any work.
4

Settle and fulfill

Once verified, /settle executes the on-chain transfer, then the original request is fulfilled — both calls typically complete in well under a second.

Visit the demo

demos.xentfi.com/modelmesh

Build it yourself

x402 Payments guide, plus the Agent tab’s x402 Reference

Nova Threads — hosted checkout

Nova Threads demo: an apparel storefront checking out a product with USDC through XentFi's hosted checkout page
Nova Threads is a streetwear storefront that accepts USDC, USDT, and ETH at checkout — no card fees, instant settlement, powered by XentFi Hosted Checkout. Add a product to cart and pay: you’re redirected to a real hosted checkout session on testnet and land back on a confirmation page once it settles. How it works:
1

Create a payment link server-side

Once the cart total is known, call the Payment Links API with the amount, currency, and a redirect URL back to the storefront.
2

Redirect the customer

Send the customer to the checkoutUrl the API returns — XentFi hosts the entire payment experience: wallet connect, network switch, confirmation.
3

Handle the return redirect

After payment, the customer lands back on the redirectUrl with status details in the query string. Fulfill the order once the payment is verified server-side.
4

Confirm via webhook

Don’t rely on the redirect alone — listen for the payment_link.paid webhook event to confirm and fulfill reliably, even if the customer closes the tab early.

Visit the demo

demos.xentfi.com/nova

Build it yourself

Payment Links guide

How the demos are built

Every demo is a small Next.js app against the XentFi sandbox, and each pairs a clickable UI with the exact integration code shown in its own Build it yourself panel — so what you click and what you’d ship are the same shape.
  • The x402 facilitator demo makes real round trips to /verify and /settle as you click through it — those two steps are a live network call, not a timer.
  • The agent wallet, auto-settlement, and deposit address demos simulate their multi-second flows (policy checks, route-finding, on-chain confirmation) client-side for a smooth walkthrough, while the code sample shown alongside each one is the real call you’d make against the API.
  • The checkout demo redirects to a genuine XentFi Hosted Checkout session on testnet, so the payment page itself is fully real.
None of the demos require an account or a wallet with funds to click through — each one is seeded with example activity so the story is visible immediately, then lets you add to it live.

Next steps

Agent Tools

Give an AI agent its own wallet and policy, like Aria.

x402 Payments

Bill AI agents per API call, like ModelMesh.

Payment Links

Add hosted checkout to a storefront, like Nova Threads.

API Reference

Every endpoint behind all five demos.