Developers Forum for XinFin XDC Network

Extending Agentic XDC Payments with x402 Micropayments

Satheesh Kumar — Wed, 17 Jun 2026 07:55:16 +0000

Introduction

Artificial Intelligence is moving from answering questions to taking action — calling tools, moving money, and completing tasks autonomously.

Rushabh's Agentic XDC Payments showed a powerful pattern: users type plain English, and an AI agent sends USDC on XDC Network without opening a wallet UI.

That demo answers one question:

"How do I pay a person on-chain?"

This project extends that idea to a second question:

"How does an AI agent pay for services on the internet — APIs, data, tools — without API keys, subscriptions, or signups?"

The answer is x402 — the HTTP 402 Payment Required standard for pay-per-use micropayments in USDC.

Instead of only sending USDC to a wallet address, the same agent can:

Call a paid FX rate API
Receive HTTP 402 with the price
Pay USDC on XDC
Retry the request with payment proof
Return the result in plain English

No account. No API key. No monthly subscription. Just pay-per-call.

What the Project Does

This is an end-to-end MVP with three parts:

Component	Role
React Chat UI	User asks in natural language
AI Agent (`Node.js`)	Parses intent, pays USDC, calls APIs
FX API Server (`Node.js`)	Serves exchange rates behind an x402 paywall

Two agent skills — one wallet

You say	What happens
"What's the GBP/USD rate?"	x402 flow: `402` → pay `0.1 USDC` → retry → FX data
"Send 1 USDC to 0xB0EF…"	Direct USDC transfer (same as the original article)

One XDC wallet. Two use cases. People and APIs.

Why x402? Why Not a Normal HTTP API?

Most APIs today work like this:

Sign up on the provider's website
Add a credit card or buy credits
Get an API key
Store and rotate that key
Pay monthly or prepay

That model was built for humans. It is awkward for autonomous AI agents.

x402 embeds payment into HTTP itself:

GET /fx/GBP-USD → HTTP 402 Payment Required → Agent pays USDC on XDC → GET /fx/GBP-USD + X-PAYMENT header → HTTP 200 + JSON data

	Traditional API	x402 API
Account required	Yes	No
API key	Yes	No
Subscription	Often	No
Pay per call	Hard	Native

The agent learns the price from the HTTP response — not from a pricing page alone.

How It Benefits the XDC Ecosystem

1. Low gas fees enable real micropayments

On high-fee chains, a $0.10 API call can cost more in gas than the payment. XDC's low fees make sub-dollar USDC payments practical.

2. USDC on XDC is the settlement layer

Network	USDC Contract
XDC Mainnet	`0xfA2958CB79b0491CC627c1557F441eF849Ca8eb1`
XDC Apothem	`0xb5AB69F7bBada22B28e79C8FFAECe55eF1c771D4`

3. Extends the agentic payments story on XDC

The original article proved:

natural language → USDC on XDC

This project proves:

natural language → pay for any HTTP service on XDC

Use cases for the XDC payments ecosystem:

Trade finance oracles — pay per price feed
RWA data APIs — micropay for FX, compliance checks
DeFi agents — buy data before executing strategies
Enterprise B2B — machine-to-machine payments on XDC rails

How It Works

Step 1 — User Input

Get me the GBP/USD FX rate

Step 2 — Agent Calls API

GET /fx/GBP-USD

Server returns HTTP 402:

{
  "x402Version": 1,
  "accepts": [{
    "scheme": "exact",
    "network": "eip155:51",
    "maxAmountRequired": "100000",
    "payTo": "0x719B...",
    "asset": "0xb5AB69..."
  }]
}

Step 3 — Agent Pays USDC on XDC

Agent sends 0.1 USDC to the API receiver wallet.

Step 4 — Agent Retries with Proof

Same request, with X-PAYMENT header containing the transaction hash.

Step 5 — User Gets the Answer

The GBP/USD exchange rate is 1.27
0.1 USDC paid → View on testnet.xdcscan.com

### Simple Flow
You    →  "What's the USD/EUR rate?"
Agent  →  calls FX API
API    →  HTTP 402 (pay 0.1 USDC)
Agent  →  pays USDC on XDC
Agent  →  retries with proof
API    →  returns FX data
You    →  gets rate + explorer link

Conclusion

This project shows they can also pay websites and APIs — via x402, USDC, and the same agent loop.

1. User expresses intent in natural language
2. Agent understands and routes the request
3. x402 handles pay-per-use API access
4. USDC settles on XDC Network
5. User gets data and an explorer link — no signup required

FuelSharp NSW — A Practical Tool for Finding Cheaper Fuel

s4njk4n — Wed, 17 Jun 2026 01:56:33 +0000

FuelSharp NSW is a free web application that helps drivers in New South Wales find the cheapest petrol stations based on official government pricing data, while also taking personal discounts into account.

What it does

The app pulls live retail fuel prices directly from the NSW Government’s public Fuel API. Key features include:

An interactive map and ranked list of fuel stations
Filtering by fuel type (U91, E10, Diesel, P95, P98)
The ability to add personal discounts (e.g. NRMA, work fuel cards, loyalty programs)
Showing the real cheapest stations after applying your discounts

It also includes an optional feature to additionally display prices in XDC or USDC (on the XDC Network) using live exchange rates. Useful to know if you're paying with XDC/USDC via a payment card.

Who it’s for

FuelSharp NSW is designed for everyday drivers in New South Wales who want to save money on fuel. It is especially useful for people who:

Regularly fill up and want to make better-informed decisions
Have access to discounts or fuel cards but find it hard to work out which station is actually cheapest after discounts
Prefer a simple, free tool without subscriptions or paywalls

The app is a Progressive Web App (PWA), so it can be saved to your phone’s home screen and used like a native app.

How it works

FuelSharp NSW fetches current pricing data from the official NSW Government Fuel Price API. Users can enter their discount amounts for different fuel station brands. The app then recalculates prices and ranks stations based on your actual cost per litre after discounts.

The XDC and USDC price display is optional and pulls live rates from public APIs. No wallet connection is required.

Data Source

All fuel price data comes from the publicly available NSW Government Fuel Price Check API. There is no commercial partnership with the government or any fuel retailer.

Try it on XDC Outpost: https://xdcoutpost.xyz

Building an AI Agent That Sends USDC on XDC Network Using Plain English

Rushabh Parmar — Thu, 11 Jun 2026 13:41:29 +0000

Introduction

Artificial Intelligence is evolving from a tool that generates information into a system capable of taking actions.

This new generation of software — often called Agentic AI — goes beyond answering questions. AI agents can understand user intent, make decisions, and interact with external systems to complete real tasks autonomously.

To explore this concept, I built Agentic XDC Payments: an AI-powered payment agent that enables users to send USDC on the XDC Network using simple natural language instructions.

Rather than interacting with wallets, smart contracts, or blockchain interfaces directly, a user simply types:

Send 1 USDC to xdc1abc...

The AI agent interprets the request, verifies the details, prepares the transaction, and executes it on-chain.

The result is a seamless bridge between human language and blockchain transactions.

What the Project Does

The application lets users initiate blockchain payments through conversation.

Instead of manually opening a wallet, selecting a token, entering an address, and configuring a transaction — users simply describe their intent.

The AI agent handles everything else:

Understanding the natural language request
Extracting the recipient address and amount
Validating the transaction parameters
Presenting a confirmation prompt
Executing the USDC transfer on XDC Mainnet

This creates an experience where blockchain payments feel as natural as messaging a digital assistant.

Technology Stack

The project combines four technologies that work together to create an end-to-end agentic payment workflow.

Claude AI

Claude serves as the reasoning engine. Its job is to analyze a natural language instruction and convert it into structured transaction data.

For example, given the input:

"Send 10 USDC to xdc123..."

Claude extracts:

{
  "action": "transfer",
  "amount": 10,
  "token": "USDC",
  "to": "xdc123..."
}

This transformation from human language into machine-readable instructions is the core of the agent.

Node.js

Node.js acts as the orchestration layer. It manages the full lifecycle — reading user input from the terminal, communicating with the Claude API, presenting confirmations, and triggering the blockchain interaction.

ethers.js

ethers.js handles all blockchain functionality: connecting to XDC Network, managing the wallet, constructing the ERC-20 transfer transaction, signing it locally, and broadcasting it to the network.

XDC Network

XDC Network is the execution and settlement layer. Once the transaction is signed, it is submitted to the XDC blockchain where it becomes a permanent, verifiable on-chain record.

How the Code Works

The project follows a clean, sequential workflow from input to on-chain settlement.

Step 1 — User Input

The terminal waits for a plain English instruction:

You > send 1 USDC to 0xB0EF2A0337A519d50780E33d268341CE75ce8383

Step 2 — AI Parsing

The instruction is sent to Claude AI. Claude analyzes the text and returns a structured JSON object containing the recipient address, token, and amount. No regex, no manual parsing — just natural language understanding.

Step 3 — Validation

Before any transaction is constructed, the application validates:

Recipient address format (supports both xdc and 0x prefixes)
Amount is a positive number within the safety limit
USDC contract is correctly loaded

This prevents malformed or unintended transactions from reaching the blockchain.

Step 4 — Confirmation

The agent displays a clear summary and requires explicit approval:

  ─────────────────────────────────────────
  To      : 0xB0EF2A...e8383
  Amount  : 1 USDC
  Gas     : ~0.01 XDC (legacy tx, 12.5 gwei)
  ─────────────────────────────────────────
  Confirm send? (yes / no):

The user remains in full control. Nothing executes without a yes.

Step 5 — Transaction Construction

Using ethers.js, the application constructs a USDC ERC-20 transfer.

Important XDC-specific settings:

const tx = await usdc.transfer(to, amountWei, {
  type: 0,                                  // Legacy tx — XDC does not support EIP-1559
  gasPrice: ethers.parseUnits("12.5", "gwei"), // XDC minimum gas price
  gasLimit: 100_000n,
});

Step 6 — Broadcast

The signed transaction is broadcast to XDC Mainnet. The blockchain validates and includes it in the next block.

Step 7 — Confirmation

The agent returns a success message with the transaction hash and a direct XDCScan link:

  ✓  Sent 1 USDC successfully!
  ✓  Tx hash : 0x17f26f8554f22a1ed2b018b584bf3f13cb2e222067a8bbdfbce7b7f0e5b5a874
  ✓  Explorer: https://xdcscan.com/tx/0x17f26f8554f22a1ed2b018b584bf3f13cb2e222067a8bbdfbce7b7f0e5b5a874
  ✓  Block   : 103647109

Live Demonstration

During testing, the agent successfully completed a live USDC transfer on XDC Mainnet.

Step	What Happened
1. Human intent	Typed: `send 1 USDC to 0xB0EF2A...`
2. AI understanding	Claude extracted address and amount
3. Safety check	Reviewed and typed `yes`
4. Autonomous execution	Agent signed and broadcast the tx
5. On-chain settlement	XDC Network confirmed in block 103,647,109

Verified transaction on XDCScan:
0x17f26f8554f22a1ed2b018b584bf3f13cb2e222067a8bbdfbce7b7f0e5b5a874

Real USDC moved on-chain through a conversational interface.

Project Structure

xdc-usdc-agent/
├── src/
│   ├── agent.js      ← CLI loop and user interaction
│   ├── parser.js     ← Claude AI intent parser
│   ├── usdc.js       ← USDC contract calls (balance + transfer)
│   └── wallet.js     ← Wallet loader (private key or mnemonic)
├── .env.example      ← Configuration template
└── package.json

Key Technical Notes for XDC Developers

If you are building on XDC Network, these constraints are important:

Use legacy transaction type 0 — XDC does not support EIP-1559 transactions
Minimum gas price is 12.5 gwei — transactions below this will be rejected
estimateGas can be unreliable — set gasLimit manually (100,000 is safe for ERC-20 transfers)
Address prefix — XDC uses an xdc prefix; convert to 0x for ethers.js using "0x" + addr.slice(3)
USDC contract on Mainnet — 0xfA2958CB79b0491CC627c1557F441eF849Ca8eb1

Why This Matters

Most AI demonstrations stop at content generation.

This project demonstrates something more meaningful: AI agents that take actions.

The future of AI is not just answering questions — it is helping users accomplish tasks. Blockchain networks provide a transparent and programmable execution layer for those tasks. By combining Claude's language understanding with XDC's on-chain settlement, developers can transform natural language directly into verifiable financial outcomes.

This pattern opens the door to more complex agentic workflows: scheduled payments, multi-step DeFi interactions, automated treasury operations — all triggered by plain English.

Open Source

The complete source code is available on GitHub:

github.com/RushabhParmar12/agentic-xdc-payments

Developers are encouraged to explore, fork, and extend the project for new agentic use cases on XDC Network.

Conclusion

Agentic AI represents a shift from software that provides information to software that performs actions.

This project demonstrates that shift in a direct, practical way:

A user expresses intent in plain English
Claude AI understands and structures the request
The application validates and confirms with the user
ethers.js signs and broadcasts the transaction
XDC Network settles it permanently on-chain

This is more than a payment application. It is a working example of how AI agents and blockchain infrastructure can combine to build the next generation of autonomous financial systems.

Built with Claude AI · ethers.js · Node.js · XDC Network

Disclaimer: This application uses AI to interpret natural language instructions. While safety checks are implemented, AI outputs may occasionally be incorrect or incomplete. Always review transaction details carefully before confirming. The user remains fully responsible for all transactions executed through this application.

Is here any developer who is able to help me for my missing funds?

Maximilian Jacobs — Mon, 08 Jun 2026 22:09:16 +0000

Need help getting access to my wallet via myethwallet and XDC network connection - no ETH

Maximilian Jacobs — Mon, 08 Jun 2026 17:24:19 +0000

[Informative] May Insights: Key Highlights and Developments from Plugin’s Journey

Pooja Balaji — Sun, 07 Jun 2026 14:05:25 +0000

As Plugin's ecosystem continues to evolve in 2026, the Plugin Decentralized Network is taking bold steps to expand the capabilities of decentralized infrastructure. This month marks a significant milestone as artificial intelligence becomes an integral part of our data feed ecosystem, enhancing how blockchain data is consumed and understood.

📰 News

🤖 Plugin Launches AI-Driven Sentiment Analysis in Data Feeds:

Plugin has taken a major leap forward with the launch of AI-Driven Sentiment Analysis in the Popular Data Feeds section of the Plugin Decentralized Network.

For the first time, real-time market sentiment scores are available directly within data feeds, providing users with valuable insight into market sentiment and emerging trends. By combining decentralized data infrastructure with AI-powered analysis, Plugin is transforming raw data into meaningful intelligence that developers, traders, and enterprises can act upon.

This innovation represents another step toward building smarter and more intuitive Web3 infrastructure.

Explore AI-powered sentiment feeds: http://feeds.plugin.global

🗺️ Plugin Roadmap 2026:

The Roadmap 2026 for Quarter 2 and 3 are now available, outlining the latest milestones, developments, and ecosystem initiatives currently underway across the Plugin Network.

Key focus areas include:

AI-powered decentralized infrastructure and Agentic AI integration
EquitEdge platform launch and regional expansion
Cross-chain interoperability and multi-chain growth
Smart Contract Automation
Website and Brand Refresh
Continued innovation in gaming, developer tools, and infrastructure enhancement.

👉 Explore the full roadmaps:https://plugin.global/resources/roadmap.html

🍽️Food for Thought:

AI is no longer a distant concept in Web3, it is becoming part of the infrastructure layer itself. As decentralized networks grow more capable, integrating intelligent data processing marks the next evolution in how on-chain information serves real users and real decisions. and sentiment is one of the most human elements of markets. The question is no longer whether AI belongs in blockchain infrastructure. It already does.

🧠 Plugin Quiz :

What does staking mean in the context of a blockchain network?

👉 Reply with your answer in the comments!

Bug Report: XDC Token Not Visible in MetaMask

Manuni Mistry — Fri, 05 Jun 2026 11:57:25 +0000

My team and I are experiencing an issue with the display of XDC token in MetaMask.

The XDC token and balance is displayed correctly when MetaMask is initially opened. However, after a few seconds the token disappears and the wallet shows a $0 balance.

When we verify the wallet address on XDCScan, the XDC balance is displayed correctly and the funds appear to be present on-chain.

Agentizing XDC Staking: A Practical First Step Toward an AI-Ready Ecosystem

Beny — Tue, 02 Jun 2026 08:45:55 +0000

As blockchain ecosystems mature, the next major shift may not come only from new applications or liquidity products. It may come from making existing infrastructure easier to understand, monitor, and use.

For XDC, a practical place to begin is staking and masternodes.

Masternodes are not just a technical feature. They are part of the infrastructure that supports network participation, reliability, and long-term ecosystem strength. Yet for many developers, institutions, and new participants, understanding how masternodes work, what they require, and how they connect to the broader XDC economy can still feel fragmented.

This is where AI agents can become useful.

Not as autonomous bots moving funds without oversight, but as a new interface layer that helps users and builders understand what is happening across the network.

From Data to Understanding

Most blockchain ecosystems already produce a large amount of information: on-chain activity, staking participation, validator data, liquidity movement, documentation, and market signals.

The challenge is that this information is often spread across explorers, dashboards, documents, and community channels.

An agent-ready ecosystem makes that information easier to navigate.

Instead of searching across multiple sources, a user could ask:

What are the current requirements for XDC masternodes?
What does staking participation look like today?
What are the risks and responsibilities?
What should builders monitor over time?
How does masternode infrastructure support the network?

This is not about replacing dashboards or documentation. It is about making them easier to use.

Why Start With Staking and Masternodes

The best place to begin agentizing an ecosystem is where better clarity creates immediate value.

XDC staking and masternodes combine infrastructure, participation requirements, operational responsibility, and economic incentives. That makes them a strong starting point for a read-only AI agent.

A first version does not need to execute transactions or control wallets. It should simply help people understand the network better.

It could explain masternode requirements, summarize staking-related information, monitor key network signals, highlight risks in plain language, and guide builders toward useful product ideas.

That alone would be valuable.

Read-Only First

There is a temptation in AI and crypto to jump directly into autonomous execution. That should not be the first milestone.

Before agents can safely interact with blockchain infrastructure, they need reliable context. Before they prepare transactions, they need accurate data. Before they act for users, they need trust and guardrails.

For XDC, the responsible path starts with read-only intelligence.

Once that foundation is trusted, agents can become more interactive: helping prepare wallet actions, create setup checklists, compare options, or connect staking data with DeFi, tokenization, and wallet activity across the ecosystem.

But the first step should be clarity.

The Builder Opportunity

For developers, agentizing XDC staking is not only about building a chatbot. It is about creating the data, tools, and interfaces that allow AI systems to understand the network correctly.

That could include agent-readable documentation, structured staking data, masternode monitoring tools, reward explainers, risk summaries, and wallet or dashboard integrations.

The opportunity is to turn XDC infrastructure into something agents can interpret and users can trust.

If the next generation of blockchain users interact through AI assistants, ecosystems that become agent-readable early will have an advantage.

Final Thought

Agentizing XDC staking and masternodes is not about chasing an AI trend. It is about making core network infrastructure more understandable and useful.

Before agents can act, they need to read. Before they can execute, they need context.

For XDC, staking and masternodes offer a practical place to begin.

The opportunity for builders is clear: make the network more agent-readable today, so it can become more agent-actionable tomorrow.

Excited to Join the XDC.dev Community

Ashish Negi — Thu, 28 May 2026 07:28:04 +0000

Glad to be part of the XDC.dev community. I work in the Lead Generation Marketing agency space, helping businesses grow through better visibility, qualified traffic, and conversion-focused strategies. Looking forward to sharing insights, learning from others, and connecting with builders and marketers here.

[Informative]How to Run an XDC Full Node behind CGNAT - Maintaining Peer Count

s4njk4n — Wed, 27 May 2026 07:59:43 +0000

If you've ever tried to run a full XDC node from home (or on a cheap VPS) and noticed your peer count stuck at 5–10 peers, you're not alone — and it's probably not your fault.

What is CGNAT?

CGNAT (Carrier Grade Network Address Translation) is a technique used by many Internet Service Providers (ISPs) to stretch the limited supply of IPv4 addresses.

Instead of giving every customer their own unique public IP address, the ISP puts hundreds or even thousands of users behind a single public IP. Your home router already does NAT, but CGNAT adds a second layer of translation at the ISP level (often called “double NAT”).

The result?

Your node can reach out to the internet, but the outside world cannot reliably reach back in to your node.

Why This Kills XDC Node Performance

XDC (like most blockchain networks) relies on a healthy peer-to-peer mesh. Your node needs to accept incoming connections from other nodes to:

Maintain a solid peer count (ideally 20+)
Stay fully synced
Contribute meaningfully to the network

Behind CGNAT, incoming connections are blocked or dropped. The result is chronically low peer counts, slower block propagation, and frustration for home node operators.

Many users on consumer broadband, mobile broadband, or certain VPS providers are silently affected without realizing it.

The Solution: XDC_Node_Behind_CGNAT

We have just released a clean, lightweight, open-source tool that automatically solves this exact problem:

XDC_Node_Behind_CGNAT

How it works:

Runs as a background service on Ubuntu/Lubuntu 26.04 (or any Ubuntu-based system)
Checks your Dockerized XDC node’s peer count every hour directly inside the container (no RPC required)
If peers drop below a configurable threshold (default = 15), it automatically runs your existing peer.sh script to inject more bootnodes
Sends a clean notification to your iOS/Android phone via ntfy.sh so you know when it kicks in
Includes simple pause and restart scripts for manual control
Starts automatically on boot via systemd
Keeps logs in the same folder and auto-trims them to stay under 1 MB

It’s designed specifically for people running the official XDC Docker node.

Perfect for:

Home lab setups
Residential fiber / cable connections
Anyone stuck behind CGNAT or strict firewalls

Get it here:

→ XDC_Node_Behind_CGNAT

The project is MIT licensed, actively maintained, and already helping XDC node operators keep their nodes healthy without needing static IPs or complex port forwarding.

If you’re tired of watching your peer count hover in single digits, give it a try — it might be the simplest quality-of-life upgrade you can make to your XDC node today.

Enjoy!

XDCE to XDC Swap — Sent to contract but XDC not received

NicolaMcD2244 — Tue, 26 May 2026 11:09:35 +0000

Hi,

I need some help please with a XDCE to XDC swap that hasn't completed. I sent XDCE to the official swap contract but have not received my XDC.

Transaction Hash: 0xe307480ab6dc98aae00f0e8492d0869291bfea67d5310fbfd84b8ed02ac3fd34

*From: *
0x48F456818e53a3a031D1A7576E156b4f4a234cDb
**
Sent to swap contract: **0x78793231c000a06c507eBa6D960CC0dEf2ed9963

Amount: 2,408.01 XDCE
Status: Successful on Etherscan

I have added XDC Network to MetaMask (Chain ID 50) and checked the XDC explorer but no XDC balance showing. xdceswap.com is also not loading.
Can anyone advise if this swap can still be processed and how to claim my XDC? Thank you.

Cheers,
Nicola

Fathom Protocol gas fee limit error

The Steel Mug Candle Co. — Sun, 24 May 2026 14:53:49 +0000

URGENT: Cannot Repay FXD Position Before June 1 Shutdown — Gas Estimation Failure on All Platforms

I am unable to repay my FXD stablecoin loan on Fathom.fi to recover my XDC collateral, and with the protocol shutting down on June 1 I am running out of time. I have tried every option I can think of and keep hitting the same wall.

What I'm trying to do:
Repay my FXD debt to close my CDP and unlock my XDC collateral before the June 1 protocol shutdown.

The error I get:

"Cannot estimate gas — transaction may fail or may require manual gas limit"

There is no way to bypass this error or manually enter a gas limit through any of the interfaces I've tried.

Everything I have tried:

SafePal mobile app (DApp browser) — Connected to app.fathom.fi, attempted repayment. Gas estimation error appears with no option to override or set a manual gas limit.
SafePal mobile with RPC switching — Tried multiple XDC mainnet RPC endpoints (erpc.xinfin.network, rpc.xdc.org, rpc1.xinfin.network). Same error on all RPCs.
Desktop browser via WalletConnect — Opened app.fathom.fi on desktop Chrome, connected via WalletConnect scanning from SafePal mobile. Same gas estimation error. No way to manually set gas limit.
Desktop browser direct — Tried connecting directly on desktop. Same result — the error blocks the transaction and there is no input field to override the gas limit.

What I need:

Either:

A working method to repay FXD and close my position before June 1, or
Confirmation that the Emergency Shutdown (ShowStopper) mechanism will be triggered on June 1 and that I will still be able to redeem my XDC collateral after shutdown

If anyone has successfully repaid an FXD position recently, or knows the correct contract address and function to call directly on XDCScan to bypass the frontend, please share. My XDC collateral is at risk of being permanently inaccessible.