#near

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

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

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.oanor.com/near-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