Models and services
Inference, retrieval and document processing run in the application or service environment. A payment receipt does not establish that an AI response is correct.
Explore the XDC AI overviewAI / CONNECTED BY XDC
Intelligence meets settlement.
Give software a practical way to pay for services. Explore AI agents, API commerce and x402 payment flows connected to XDC Network.
WHERE XDC FITS
Reason off-chain. Settle on XDC.
An AI model can choose or generate an action. A wallet authorizes payment, and the network records the resulting transaction. These are different responsibilities.
Authorization and controls
Define which services an agent may call, what it may spend and when a person must approve an action. Custody and enforceable limits depend on the wallet and provider configuration.
Provider spending-limit guidePayment and records
XDC can record USDC transfers and contract state. Keep request identifiers and service receipts alongside transaction evidence so an application can reconcile payment with delivery.
Explore XDC payment infrastructureTHE X402 PAYMENT FLOW
A service request with payment built in.
x402 uses HTTP payment negotiation. The exact headers, supported networks and verification steps depend on the selected protocol version and facilitator.
Request the service
An application or agent calls an API. If payment is required, the server returns HTTP 402 with its payment requirements.
Protocol introductionCheck and authorize
The client checks the asset, network, recipient, price and authorization policy before signing the required payment payload. Approval rules belong in the application’s control layer.
Verify and settle
The server and its selected facilitator validate the payment and perform settlement. A signature, a verification response and an on-chain settlement are distinct states.
Deliver and reconcile
The service returns its result under its settlement policy. Match delivery to the payment record and handle retries or refunds according to the provider’s documented behavior.
XDC-FOCUSED DESIGN PATTERNS
Build services that can transact.
These examples describe application opportunities. They are not announcements of deployed products or guaranteed outcomes.
Illustrative pattern
Pay-per-request data
An agent can purchase a specific data response instead of maintaining an open-ended subscription. Show the quote and source before authorizing the request.
Illustrative pattern
Trade-document services
A workflow could pay an API to classify or extract information from trade documents. Keep sensitive documents off the public ledger and require human review for consequential decisions.
Illustrative pattern
Paid inference and tools
Offer a model endpoint or specialist tool through a paid API. The provider delivers the compute; XDC supplies the payment record for the chosen integration.
Illustrative pattern
Agent-assisted operations
An assistant can read network data, prepare reports and propose actions. Keep write permissions and spending authority separate from read-only analysis.
CHOOSE YOUR STARTING POINT
For service builders. For agent builders.
Start with one integration and a small test scope. A marketplace listing, a payment protocol and a blockchain are separate parts of the system.
Offer a paid API
Document the request, response, price and service terms. Integrate the chosen x402 version, verify settlement behavior and test retries before offering access.
Public facilitator documentationConnect an agent
Choose the wallet model and supported network. Configure recipient and spending policies, then verify how to pause or revoke authority in that implementation.
XDC AI platformConnect the wider application
Combine payment with your existing backend, user experience and event handling. Use the XDC developer hub for the underlying network configuration.
Build on XDCA few useful answers
Common questions.
Does XDC execute AI models on-chain?+
The application patterns described here use off-chain AI services. XDC handles transactions and contract execution. This guide does not claim a protocol-level inference engine or decentralized GPU service.
Is x402 only for AI agents?+
No. An ordinary application or HTTP client can use a compatible x402 flow. Agents are one potential client of a paid API.
Does gasless mean the network has no fees?+
No. In a supported sponsored flow, a facilitator or relayer pays the network fee. The payer experience and sponsorship conditions depend on that service; ordinary XDC transactions still require gas.
Can I assume every integration has the same custody and spending limits?+
No. Provider pages describe different wallet and control configurations. Verify key ownership, supported limit enforcement, revocation and protocol version for the actual integration.
Does settlement prove that a service delivered the right answer?+
No. Settlement proves the payment outcome, not the correctness or quality of a response. Applications need their own service checks, receipts and dispute process.
Go to the source
Sources & further reading.
KEEP EXPLORING