Chain status: latest block, chain id, node version
API · /nibiru-api
Nibiru Chain API
Real-time on-chain data for Nibiru (chain-id cataclysm-1), a Cosmos-SDK Layer-1 for DeFi with a native EVM, secured by delegated proof-of-stake with NIBI as its native coin. The status endpoint returns the chain id, latest block height and time, proposer and node application version so you can confirm the chain is live and producing blocks. The validators endpoint returns the full bonded validator set — each moniker, operator address, stake in NIBI, commission rate and jailed flag — sorted by stake, plus the total bonded and not-bonded NIBI. The supply endpoint returns the total NIBI supply (in NIBI and base unibi), the bonded amount and the bonded ratio. The governance endpoint returns the most recent on-chain governance proposals with title, status and voting window. The meta endpoint documents the chain, denom and decimals. Reads a live Nibiru Cosmos-SDK LCD node directly (with mirror fallback), so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves chain-level staking, supply and governance data; for token prices or smart-contract reads use a dedicated market/contract API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 87 ms
- Server probes · 24h
- Subscribers
- 4,735
- active
- Total calls
- 0
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 290 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 290 calls/month
- 2 req/sec
- All 5 endpoints
- Live Nibiru chain data
Basic
€13.60 /month
- 24,500 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 24.5k calls/month
- 5 req/sec
- Validators + supply
- Governance feed
- Email support
Pro
€35.40 /month
- 128,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 128k calls/month
- 20 req/sec
- High-volume access
- Priority routing
- Priority support
Mega
€78.90 /month
- 575,000 calls / month
- 60 requests / second
- Hard cap (429 above quota, no overage)
- 575k calls/month
- 60 req/sec
- Dedicated throughput
- SLA-backed uptime
- Direct support
Built by
Related APIs
Other APIs with overlapping tags.
Morph Chain API
Real-time on-chain data for Morph (chain-id 2818), a consumer-focused Ethereum Layer-2 built on an optimistic-zkEVM hybrid rollup, where gas is paid in ETH. The status endpoint returns the chain id, network id, latest block height, native symbol and node client version so you can confirm the chain is live and synced. The block endpoint returns a block by decimal or 0x-hex height — or the latest block when no height is given — with its hash, parent hash, timestamp (raw and ISO), transaction count, gas used and limit, base fee and miner. The gas endpoint returns the current gas price in both wei and gwei at the latest block. The balance endpoint returns the native ETH balance (in wei and human-readable units) and the transaction count (nonce) for any 0x address. The meta endpoint documents the chain id, decimals and ecosystem. Reads a live Morph JSON-RPC node directly, so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves native-coin and chain data; for ERC-20 token balances or contract calls use a dedicated token/contract API.
api.oanor.com/morph-api
Passage Chain API
Real-time on-chain data for Passage (chain-id passage-2), a Cosmos-SDK Layer-1 for gaming, the metaverse and NFTs, with PASG as its native coin, secured by delegated proof-of-stake. The status endpoint returns the chain id, latest block height and time, proposer and node application version so you can confirm the chain is live and producing blocks. The validators endpoint returns the full bonded validator set — each moniker, operator address, stake in PASG, commission rate and jailed flag — sorted by stake, plus the total bonded and not-bonded PASG. The supply endpoint returns the total PASG supply (in PASG and base upasg), the bonded amount and the bonded ratio. The governance endpoint returns the most recent on-chain governance proposals with title, status and voting window. The meta endpoint documents the chain, denom and decimals. Reads a live Passage Cosmos-SDK LCD node directly (with mirror fallback), so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves chain-level staking, supply and governance data; for individual NFTs or game assets use a dedicated indexer API.
api.oanor.com/passage-api
BitSong Chain API
Real-time on-chain data for BitSong (chain-id bitsong-2b), a Cosmos-SDK Layer-1 built for the music industry — music NFTs, artist fan tokens and streaming — with BTSG as its native coin, secured by delegated proof-of-stake. The status endpoint returns the chain id, latest block height and time, proposer and node application version so you can confirm the chain is live and producing blocks. The validators endpoint returns the full bonded validator set — each moniker, operator address, stake in BTSG, commission rate and jailed flag — sorted by stake, plus the total bonded and not-bonded BTSG. The supply endpoint returns the total BTSG supply (in BTSG and base ubtsg), the bonded amount and the bonded ratio. The governance endpoint returns the most recent on-chain governance proposals with title, status and voting window. The meta endpoint documents the chain, denom and decimals. Reads a live BitSong Cosmos-SDK LCD node directly (with mirror fallback), so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves chain-level staking, supply and governance data; for individual fan tokens or music NFTs use a dedicated indexer API.
api.oanor.com/bitsong-api
cheqd Chain API
Real-time on-chain data for cheqd (chain-id cheqd-mainnet-1), a Cosmos-SDK Layer-1 purpose-built for decentralised identity, verifiable credentials and trust registries, with CHEQ as its native coin (base denom ncheq, 9 decimals), secured by delegated proof-of-stake. The status endpoint returns the chain id, latest block height and time, proposer and node application version so you can confirm the chain is live and producing blocks. The validators endpoint returns the full bonded validator set — each moniker, operator address, stake in CHEQ, commission rate and jailed flag — sorted by stake, plus the total bonded and not-bonded CHEQ. The supply endpoint returns the total CHEQ supply (in CHEQ and base ncheq), the bonded amount and the bonded ratio. The governance endpoint returns the most recent on-chain governance proposals with title, status and voting window. The meta endpoint documents the chain, denom and decimals. Reads a live cheqd Cosmos-SDK LCD node directly (with mirror fallback), so values are current to the latest block. Live, nothing stored. 5 endpoints. This serves chain-level staking, supply and governance data; for DID documents or credential resolution use a dedicated cheqd resolver API.
api.oanor.com/cheqd-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Nibiru Chain API?
What's the rate limit for Nibiru Chain API?
How much does Nibiru Chain API cost?
Can I cancel my subscription anytime?
Is Nibiru Chain API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/nibiru-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/nibiru-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/nibiru-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/nibiru-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.