REBORNCHAINS
DEVELOPER RESOURCES

Public API

Blockchain data for KAGA and MNVIP. Read-only JSON endpoints, one network at a time.

Getting started

Send an HTTP GET request to an endpoint below. No API key is currently required. JSON responses contain live node statistics and data from the RebornChains index.

Recommended polling interval: 10 minutes (600 seconds) per coin. This is a client-side recommendation, not a server-enforced limit or a promise that responses are cached for ten minutes.

Base URL: http://156.67.31.246. The API is currently served over HTTP. An HTTPS website should fetch it through its own backend; browsers block HTTPS-to-HTTP fetches as mixed content.

Statistics response

Illustrative KAGA response. Values and timestamps are examples, not current network data. MNVIP uses the same structure, with coin and symbol set to MNVIP.

{
  "coin": "KAGA",
  "symbol": "KAGA",
  "status": "online",
  "blockchain": {
    "height": 31597,
    "supply": 789924.5577465,
    "difficulty": 1888.980705566925,
    "connections": 10
  },
  "masternodes": {
    "active": 88,
    "total": 88,
    "lockedCoins": 440000,
    "collateralOutputs": 88,
    "collateralCheckedAt": "2026-10-30T09:03:14.586Z",
    "lockedPercent": 55.7,
    "roiAnnualPercent": 308.22,
    "roiEstimate": {
      "method": "Annualized gross reward / active collateral",
      "averageBlockSeconds": 348.81,
      "blockIntervals": 1000,
      "firstHeight": 30597,
      "lastHeight": 31597,
      "assumedMasternodeRewardPerBlock": 15,
      "rewardSampleHeight": 31594,
      "assumptions": "Assumes every future block pays 15 KAGA to active masternodes, with unchanged block pace and active collateral. Excludes costs and compounding; actual payouts vary."
    }
  },
  "explorer": {
    "syncedHeight": 31597,
    "storedBlocks": 31597,
    "storedTransactions": 62901,
    "syncProgress": 100,
    "fullySynced": true
  },
  "updatedAt": "2026-10-30T09:03:14.936Z"
}

Reading the data

FieldMeaning
blockchain.heightCurrent height reported by the coin node.
blockchain.supplyCoin supply reported by the node, in whole-coin units.
blockchain.difficultyCurrent network difficulty.
blockchain.connectionsPeer connections of our node; not the total number of nodes worldwide.
masternodes.active / totalEnabled and total masternodes reported by the node.
masternodes.lockedCoinsVerified unspent collateral in unique outputs of enabled masternodes.
masternodes.lockedPercentVerified active collateral divided by supply, as a percentage.
masternodes.collateralCheckedAtUTC timestamp of collateral verification; results are cached for up to five minutes.
masternodes.roiAnnualPercentEstimated annual gross reward relative to active collateral; not guaranteed yield.
masternodes.roiEstimateMeasured block interval, sample window and reward assumptions used for ROI.
explorer.syncedHeightHighest block stored in the explorer index.
explorer.storedTransactionsIndexed transaction count derived from stored block transaction counts.
explorer.syncProgress / fullySyncedIndex progress relative to our node. This does not independently verify that the node itself is caught up with the network.
updatedAtUTC time the statistics response was generated. Individual metrics may be cached or have different observation times.

Optional metrics may be null or absent. Treat these as unknown, never as zero. ROI requires 1,000 contiguous indexed block intervals, a near-current index and verified active collateral. It assumes 15 KAGA or 4.5 MNVIP per future block for masternodes and excludes costs and compounding.

Block heights and timestamps in indexed block and transaction responses may be encoded as strings. Accept additional JSON fields to keep integrations compatible with future extensions.

Additional endpoints

Replace {coin} with lowercase kaga or mnvip. All endpoints below are read-only GET requests.

PathResponse
/api/{coin}/statusNode summary: coin, status, blocks, peers and other node fields.
/api/{coin}/blocks?limit=20{"coin":"KAGA","count":20,"blocks":[...]}. Default limit 20; supported range 1–100.
/api/{coin}/block/{height}{"coin":"KAGA","block":{...},"transactions":["txid",...]}. Indexed block heights start at 1.
/api/{coin}/tx/{txid}{"coin":"KAGA","transaction":{...}}. Requires a 64-character hexadecimal transaction ID already present in the index.

Transaction details can include input/output amounts, fee and net staking reward. Raw output amounts include returned staking principal and must not be interpreted as pure rewards. Missing historical inputs make dependent totals unknown. If raw enrichment fails, indexed metadata can still be returned with detailsUnavailable.

Usage examples

Fetch either coin from your server:

curl --fail --max-time 20 http://156.67.31.246/api/kaga/stats
curl --fail --max-time 20 http://156.67.31.246/api/mnvip/stats

Node.js 20+ example. Fetches immediately and then every ten minutes; failed requests do not overlap:

const url = 'http://156.67.31.246/api/kaga/stats';

async function poll() {
  try {
    const response = await fetch(url, {
      signal: AbortSignal.timeout(20000),
      headers: { Accept: 'application/json' }
    });
    if (!response.ok) throw new Error(`HTTP ${response.status}`);
    const data = await response.json();
    console.log(data);
    // Store or display the data in your application.
  } catch (error) {
    console.error('Statistics unavailable:', error.message);
  } finally {
    setTimeout(poll, 600000);
  }
}

poll();

Access and errors

Server-to-server access: available without a browser CORS requirement. Direct browser requests from other websites are not currently enabled by an API CORS policy. Use your own backend to fetch, cache and serve the data to your website.

HTTP 200 indicates a successful response; optional fields can still be unknown. HTTP 400 indicates invalid input, 404 an unknown or unindexed record, and 500/503 a backend or node failure. Nginx may return 502/504 or an HTML error page when the upstream is unavailable. Check the HTTP status before parsing JSON.

Do not interpret an outage as a zero balance or zero supply. Keep the last successful response with its timestamp and mark stale data. Avoid rapid retries; poll each coin no more often than once every ten minutes for third-party integrations. Availability and response fields may change as the service evolves.