Open XDC AI
Set up your provider account.
Agentic commerce · x402
Payment rails for AI agents
Connect an agent, discover useful services and pay per call in USDC on XDC.
On this page
Explore the expanded XDC guide to agent payments, application design and integration choices. AI & agents on XDC →
XDC AI combines a service marketplace, agent integrations and x402 payment infrastructure. A compatible agent can discover an endpoint, receive its price and make an authorized USDC payment to request the result.
Sponsored settlement uses a relayer to pay XDC gas. Wallet custody, funding and spending controls depend on the provider’s account configuration; review the wallet guide when setting up access.
A practical starting point
Browse services
Discover the current marketplace.
Read the documentation
Explore accounts, agents and APIs.
From account to paid API call
01 · Set up your account
Complete the provider’s login and wallet setup. Review the selected custody model and activate the controls you need.
02 · Fund with USDC
Use the receiving address shown by the provider and send supported USDC on XDC mainnet.
03 · Connect an agent
Use the MCP connector for supported chat environments or the CLI in a compatible terminal environment.
04 · Discover, call and pay
Find a service, review its price and make an authorized call. The payment-aware client handles the x402 request flow.
Fund the work your agent does
Funding
Deposit USDC
Send supported native USDC on XDC to the account address. The relayer sponsors gas for the described payment flow.
Provider integration
Borrow against XDC
The original XDC introduction announced collateral-backed funding as coming soon. The provider now documents lending and borrowing integrations; consult its current guide for supported account flows and availability.
See current provider availability
Understand the wallet you enable
The provider’s detailed wallet guides describe a custodial account flow and an optional Safe-based smart wallet with a USDC allowance per period. These are distinct configurations; a basic account is not automatically protected by an on-chain cap.
Account dashboard
Balances, funding addresses, transaction history and approved payees.
Spending limits
Enable a period-based USDC allowance, move funds into the configured smart wallet and manage agent access. Per-transaction and native-XDC caps are described as roadmap items.
What could your agent pay for?
These examples describe possible services. Available actions, providers and prices are shown in the current marketplace.
Send & receive
USDC payouts and transfers within the provider’s supported authorization and recipient controls.
Swap assets
A service can expose supported token swaps with a quoted transaction flow.
Book a hotel
A travel service could expose room search, confirmation and payment.
Book flights
A booking integration could quote fares and accept payment when a ticket is purchased.
Order food
A commerce endpoint could handle an order and checkout.
Build your own service
Wrap an API in compatible x402 payment middleware and publish its capabilities.
Connect through MCP
The XDC AI MCP service exposes account, discovery and payment tools to compatible chat applications. Follow the provider’s instructions for your application’s current connector interface.
Connection endpoint
MCP endpoint
https://api.xdcai.tech/mcp
Documentation
Claude.ai & ChatGPT guide
Connector setup and supported tools.
Workflow
Discover before paying
Search the marketplace, inspect the service and call the selected URL. The provider’s connector handles payments through the paid-call tool rather than exposing unrestricted transfers.
Use your terminal agent
The xdcai CLI is documented for environments such as Claude Code, Cursor, Codex and a standard terminal. The original network introduction also names Hermes and Clawbot among agent environments.
| Item | Details |
|---|---|
Authenticate CLI | npx xdcai login — authenticate with the provider. Accept its terms only after reviewing them. |
Get the funding address CLI | npx xdcai wallet address — retrieve the address for the configured account. |
Check the balance CLI | npx xdcai wallet balance — inspect available balances. |
Find a service CLI | npx xdcai marketplace list — inspect the catalog and select the relevant endpoint. |
Make an authorized call CLI | Use the documented call command with a selected service URL. The client processes supported 402 challenges and returns a structured result. |
| Documentation | Setup, commands, session management and output format. |
Built for agent workflows
EIP-3009 authorizations
The agent signs a supported USDC payment authorization; a relayer submits it and pays network gas.
Structured output
CLI commands return machine-readable JSON. Errors use structured output and a failure exit code.
MCP & skill discovery
MCP tools and a skill manifest let supported agents discover capabilities and follow the integration workflow.
Open x402 payments
The integration uses the x402 exact-evm payment scheme and compatible resource-server or facilitator components.
Wallet adapters
The original architecture describes adapters for HD, MPC, smart-account and custodian integrations. Available configurations are documented by the provider.
On-chain records
Payments settle as USDC transfers on XDC, with transaction hashes available for inspection.
Turn an API into a paid service
01 · Describe the service
Publish what the endpoint does, its inputs and its price.
02 · Add payment handling
Use compatible middleware to return 402 requirements and verify paid requests.
03 · Configure settlement
Set the supported network, USDC payment configuration and provider payout address.
04 · List and operate
Submit the service to the marketplace and maintain its documentation, pricing and availability.
Human-approved DeFi actions
The provider’s current documentation describes Fathom and PrimeFi supply, withdrawal, borrowing and repayment, plus supply and withdrawal through Morpho and Silo. An agent proposes a fund-moving action; the user reviews it in the browser, completes the required authentication and signs. A proposal alone does not move funds.
DeFi documentation
Supported protocols, collateral requirements and review/sign workflow.
Give your agent the setup guide
The provider publishes a machine-readable setup document at xdcai.tech/setup.md. Review the current instructions and connect the account using the supported workflow.
Open the setup guide
Provider-maintained integration instructions.
Choose an integration
Agent connection options.
Before your first paid call
Do I need XDC for gas?
The described XDC AI payment flow sponsors gas through a relayer, so the payer funds supported USDC. Other blockchain actions may have different requirements.
Is every account non-custodial?
No universal custody claim applies here. The detailed provider guides distinguish a custodial account from an optional smart-wallet configuration. Review those guides for the flow you enable.
Are on-chain spending caps automatic?
The provider’s spending-limit guide describes them as opt-in. Configure the smart wallet and its allowance before relying on a cap.
Does connecting an agent authorize unlimited payments?
A connection should be configured around the calls and budget you authorize. Review the provider’s controls, service pricing and recipient rules.
Can an agent execute a DeFi proposal by itself?
The documented DeFi flow requires user review, authentication and a wallet signature. The agent’s proposal is not a completed transaction.
Are the travel and commerce examples all live services?
They are examples of possible x402 services. Consult the marketplace for currently listed providers and capabilities.
Developer support
Developer documentation
Network integration, smart contracts and node operations.
XDC developer forum
Ask questions, share a tutorial or connect with other builders.
Developer Telegram
Join the XDC technical community.
CodeRun AI
AI development tools and technical support for building on XDC.
SOURCE & CONTEXT
Content carried forward from XinFin’s public website and linked primary sources. Historical material is identified where applicable.
Source record Editorial methodology