NEARpedia is a live knowledge layer for AI agents building on NEAR. It syncs NEAR's docs, packages, repositories, release notes, RPC and governance, and tells an agent when its code uses something NEAR removed, deprecated or changed, with the source and the date.

How does an agent use it?

Through MCP at https://near-pedia.xyz/mcp (no key) or the REST API: check_code checks a file, check_deprecation and resolve_package check a name or a package version, get_radar lists what is changing now.

Where do the answers come from?

From NEAR's own sources: docs.near.org, npm and crates.io, the NEAR GitHub organisations and their release notes, mainnet and testnet RPC, the House of Stake contracts, gov.near.org, NEAR Catalog and DefiLlama.

12 of 12 sources syncing

What NEAR looks like today.

NEAR moves faster than anyone's memory. NEARpedia tracks what it removed, deprecated, changed and voted on, for the agents writing NEAR code and the people researching NEAR, with a source and a date on every answer.

Every answer cites its source
Re-synced 5 min – 24 h
MCP + REST, no key

MCP · no key REST API · open

Knowledge layer

12 SOURCES · SYNCING

27MCP TOOLS-AVG LATENCY● SERVER

GitHub issues3,186 Releases1,328 Repositories808 npm + crates.io90

TOTAL INDEXED RECORDS
12 of 12 sources · full-text search

11,878records

12 sources5 min – 24 h sync/api/v1/sourcesFree, no API key

START WHERE YOU ARE

Two ways in.

FOR BUILDERS

Is my NEAR code current?

SDKs, packages, RPC methods and protocol features NEAR removed or replaced, each with its evidence and what to use instead, plus the docs, release notes and open issues behind them.

Connect an agent (MCP)Deprecations Docs Releases Open issues and PRs

FOR RESEARCHERS

What is happening on NEAR?

Protocol upgrades and the validator vote, House of Stake proposals, incidents, projects and the forum, each alert gone once it resolves, and a chat that answers from these sources.