Documentation

Build on XDC with Plugin data

Get started with any product, look up every public HTTP API, and integrate feeds with the open-source FeedKit templates.

1 · Read a feed on chain

Works today: no key, no sign-up. Read the proxy, check updatedAt, call decimals().

bash

cast call 0x2baa1AEfa06D58454c9c06C56436CdD5B7904248 "latestRoundData()(uint80,int256,uint256,uint256,uint80)" --rpc-url https://erpc.xinfin.network

Solidity and viem examples FeedKit

2 · Use the tested adapter

FeedKit's checked adapter reverts on stale, zero, incomplete or access-controlled reads, with per-feed staleness defaults. The feed list is also published as feeds.json.

FeedKit Feed table

3 · Query the JSON API and MCP

Works today: no key, no sign-up. The JSON snapshot and AgentGateway's read-only MCP tools for Plugin feeds and XDC data.

bash

curl -s https://feedplumb.com/api/feeds.json | jq '.feeds[] | select(.pair=="XDC/USDT") | {price, status, ageS}'

Feeds API MCP reference

Conventions

Base URL	`https://feedplumb.com` (every API is a path on this domain)
Format	JSON over HTTPS unless stated (supply endpoints also serve plain text; statements CSV/PDF).
Auth	Most reads are open. Paid or private APIs use a header key: `x-api-key` (EventHook, DataQuery, RouteQuote) or `x-tenant-token` (FeedHealth).
Limits	Per-IP rate limits per API (listed on each page). Please cache and back off on `429`.
Safety	No API signs or broadcasts mainnet transactions. Alert and webhook delivery starts when each product launches. Admin routes are not reachable from the internet.
Fresh / stale	One rule for every product: a feed is stale when its last update is older than 1.5 × its heartbeat. The heartbeat is Plugin's published heartbeat or, when none is published, the one FeedKit assumes (30 minutes for most crypto pairs, 24 hours for daily FX, stock and metal feeds). FeedKit's on-chain adapter also has a separate revert cutoff (`maxStaleness`, per-feed defaults in its table); for a feed that is not in its table you pass your own (0 reverts).
Addresses	XDC explorers show addresses as `xdc…`. This is display-only: on chain, in Solidity, viem, ethers and Foundry, use the same address with `0x`. FeedPlumb APIs accept either form; examples use checksummed `0x`.
Privacy	No cookies, no tracking. See the privacy notice.

API reference

14 APIs, all with curl examples.

Feeds API

/api

JSON snapshots refreshed about every 5 minutes: every known Plugin feed on XDC mainnet with price, status, owner and history.

8 endpoints · auth: none

EventHook API

/notify

Subscribe to XDC contract events or ERC-20/XRC-20 transfers and receive HMAC-signed HTTPS POSTs after 5 confirmations.

5 endpoints · auth: API key

DataQuery API

/data

Pay-per-call access to indexed feed history, token and pool data, using prepaid, off-chain, non-transferable credits.

8 endpoints · auth: API key

RouteQuote API

/route

Best-route DEX quotes on XDC mainnet across XSwap V2/V3, Oku and Curve, from eth_call simulations.

3 endpoints · auth: key for quotes

AttestHub API

/attest

Read API and explorer for EAS 1.9.0 attestations.

4 endpoints · auth: none

NodeAlert status API

/nodewatch

Public status page and JSON for XDC masternode and Plugin node checks: uptime, signing lag, missed rounds, penalties and upgrade readiness.

2 endpoints · auth: none

FeedHealth API

/feed-health

Private, per-tenant feed-health pages and status JSON (white-label).

4 endpoints · auth: tenant token

Supply API (ListingReady)

/supply

Total and circulating supply in the format listing sites expect, a Uniswap-format token list and a live listing-readiness report, read on chain at one block.

6 endpoints · auth: none