Account balance + contract flag
API · /near-api
NEAR Protocol API
Live on-chain data from the NEAR Protocol (NEAR), a sharded proof-of-stake Layer 1 known for its human-readable named accounts and its access-key permission model, via a public NEAR RPC endpoint. On NEAR an account is a name like "aurora" or "example.near", not a hash, and each account authorises actions through access keys that are either full-access or function-call-scoped. Resolve an account's NEAR balance, the portion locked for staking, its storage usage and whether it holds a deployed contract. Read the account's access keys with each key's permission — full access, or a function-call key with its allowance, the contract it may call and the methods it is limited to. Get the current validator set ranked by stake, with each validator's blocks produced versus expected. Read the live chain state — the chain id, protocol version, latest block height, gas price, validator count and total stake. Live, no key, nothing stored. Distinct from the XRP Ledger, Stellar, TRON, Aptos, Algorand, Tezos, Cardano, Hedera, Kaspa, Cosmos, Sui, Solana and EVM on-chain APIs and from price feeds — this is NEAR's named-account state, access keys, staking validators and chain economics. Perfect for wallets, explorers and analytics apps.
API health
degraded- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 3176 ms
- Server probes · 24h
- Subscribers
- 4,287
- active
- Total calls
- 80
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 8,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 8k calls/month
- 2 req/sec
- Account + keys + validators + network
- No credit card
Starter
€14.00 /month
- 152,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 152k calls/month
- 5 req/sec
- Email support
Pro
€40.00 /month
- 905,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 905k calls/month
- 15 req/sec
- Priority support
Business
€86.00 /month
- 4,650,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 4.65M calls/month
- 40 req/sec
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
NEAR Validators & Staking API
Read NEAR's validator set and network economics live from a public NEAR RPC endpoint — no key. NEAR is sharded proof-of-stake: validators stake NEAR, produce blocks and chunks across shards, and earn rewards. The NEAR on-chain reader resolves a single account's state and the view reader runs contract view methods, but neither surfaces the validator set, the next-epoch staking proposals, or the live network economics. This opens that. List the current epoch's validators ranked by stake — each with its account id, stake in NEAR, the blocks and chunks it produced versus expected (its uptime) and slash status; read the next-epoch staking proposals (the validators entering, leaving or re-staking for the upcoming epoch); and read the live network economics — the gas price (in yoctoNEAR), the epoch length in blocks, the protocol version and the block/chunk producer kickout thresholds. The validator / staking / network layer for NEAR explorers, staking dashboards, delegators and analytics. Distinct from the NEAR on-chain account reader and the NEAR view-function reader. Live from RPC; short cache only.
api.oanor.com/nearvalidators-api
NEAR View API
Execute read-only contract view methods on NEAR, live, via public NEAR RPC — no key. This is NEAR's equivalent of an eth_call: run any contract's view method against the current chain state and get its return value, with no transaction, gas or signer. Call a method by name with JSON arguments on any contract, or use the convenience endpoints for a NEP-141 fungible token's metadata and total supply and for any account's token balance. Read whatever a NEAR contract exposes — token data, AMM pool reserves, registry lookups, DAO and staking state — straight from the source, with the byte result decoded from JSON for you. The on-chain read layer every NEAR wallet, dashboard, trading bot and indexer needs. Live from the chain; short cache only.
api.oanor.com/nearview-api
Aurora Chain API
Live on-chain data for Aurora — an EVM running on the NEAR Protocol — via its public Blockscout explorer (no wallet, no key). The stats endpoint returns chain-wide totals (blocks, transactions, addresses, average block time, gas used); gas gives the current gas-price oracle (slow/average/fast). Blocks lists the latest blocks, and a single block resolves by height or by hash with its transaction count, gas, miner and timestamp. The address endpoint returns any account's ETH balance, nonce, contract flag and token holdings; transaction resolves a tx by hash with its from/to, value in ETH, fee, status and block. The token endpoint returns an ERC-20 token's metadata (name, symbol, decimals, total supply, holders) by contract address, and search runs a universal lookup across addresses, tokens, blocks and transactions. Gas, balances, values and fees are denominated in ETH, the native coin. Real on-chain data straight from the explorer, refreshed every call — no key. 9 endpoints. For multi-chain coverage combine with the other oanor chain APIs (Ethereum, Base, Arbitrum and more).
api.oanor.com/aurora-api
Meter API
Live EVM on-chain data for Meter (chain id 82) — the HotStuff-BFT proof-of-stake Layer-1 whose native gas token is MTR — served directly from public EVM JSON-RPC nodes with multi-node failover. The status endpoint returns the chain and network id, the latest block height and the node client version. The block endpoint returns a block by number (or the latest) with its hash, parent hash, timestamp, transaction count, gas used and gas limit, miner and size. The gas endpoint returns the current gas price in both wei and gwei. The balance endpoint returns the MTR balance and outgoing transaction count for any address, converted from base wei (18 decimals) into whole MTR with exact big-integer scaling. Every figure is read live from the chain over JSON-RPC — nothing bundled or modelled — behind a short server-side cache with keep-warm so the feed stays fast and fresh. Ideal for explorers, wallet and dashboard tooling, gas trackers, address monitors and analytics apps across the Meter ecosystem. Live keyless upstream. 5 endpoints.
api.oanor.com/meter-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for NEAR Protocol API?
What's the rate limit for NEAR Protocol API?
How much does NEAR Protocol API cost?
Can I cancel my subscription anytime?
Is NEAR Protocol 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/near-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/near-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/near-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/near-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.