Agent DeFi Settlement Rail

Agent-native payment infrastructure for $U on BSC.

A public x402 facilitator for real merchant commerce. Agents sign one EIP-3009 authorization, merchants verify before serving, and settlement lands directly in each merchant wallet while the rail stays transparently observable in real time.

Launch Merchant Workspace Read Quickstart

Non-custodial

Merchant-owned payTo

Funds never park in the facilitator. Every project settles straight to its configured wallet.

Project scoped

Keys and telemetry per merchant

Self-serve signup, project creation, API key rotation, and project-level payment monitoring.

Realtime

Public proof of activity

Transparent platform stats, settlement flow, and live updates over Server-Sent Events.

BSC mainnet only $U native EIP-3009 Agent checkout ready Merchant-scoped payTo Session-based console SSE transparency feed BSC mainnet only $U native EIP-3009 Agent checkout ready Merchant-scoped payTo Session-based console SSE transparency feed

1. Payer

Signs intent

The payer signs a precise EIP-3009 authorization with amount, recipient, expiry, and nonce.

2. Merchant

Calls verify

The merchant checks signature validity, funds, replay state, expiry, and the project-owned payTo before serving.

3. Facilitator

Tracks state

Verification IDs, idempotent settlement records, project separation, and live rail telemetry stay in sync.

4. Wallet

Receives $U

Settlement is non-custodial. Funds move directly from payer to the merchant project's wallet.

Live platform stats

Observe the rail while it moves value.

Every number below is sourced from the same facilitator state that merchants use for verify and settle.

Agent payers

Unique payer wallets seen on successful payment paths.

Value facilitated

Cumulative U settled by the public facilitator.

Confirmed tx

Total successful on-chain settlement transactions.

Active merchants

Merchants with active projects on the current rail.

Flow map

Latest settled payments

Recent confirmed settlements fan out by project so you can see which commerce lanes are actually alive.

Waiting for live activity...

Execution mix

Rail outcomes

Confirmation, pending, and failure states stay visible so merchants can inspect operational quality in public.

Waiting for live activity...

Why this platform exists

Built for merchants that want agent payments without giving up custody.

Public trust surface

We expose platform stats, recent payments, and settlement state so integrators can inspect the rail instead of trusting marketing copy.

Merchant-owned settlement

Every project has its own API key and its own payTo. The facilitator coordinates the rail, but the merchant owns the destination wallet.

Agent-native execution

We focus the rail on BSC, U, and EIP-3009 so the payment path stays narrow, fast, and optimized for automated commerce.

What merchants get

A console, a feed, and a payment API from the same source of truth.

Self-serve onboarding

Create an account, onboard a project, and receive an API key immediately from the Merchant Console.

Project-level visibility

Monitor payers, total facilitated value, payment outcomes, and project-specific live updates in one place.

Ops-friendly key rotation

Rotate project API keys without leaving the console, while the facilitator keeps settlement and idempotency constraints intact.

Transparency feed

Recent facilitated payments

Inspect merchant activity, payer distribution, and settlement outcomes without logging in.

Status	Merchant	Payer	Amount	Updated	Transaction
Loading live activity...

For merchants and agent builders

Use the same rail for onboarding, monitoring, and settlement.

The facilitator is already live on BSC mainnet. If you want an agent-facing payment rail for U, the shortest path is to create a merchant workspace, provision a project, and start calling quote/verify/settle.

Open Merchant Console Integration Guide