Loops HouseNEARpedia

NEAR HACKATHON
Links
Team
1 member- OLOwner
Oleksii 0xFearless
Overview
AI agents write NEAR code from what they remember, and NEAR keeps moving: near-sdk-js was archived on 30 October 2026, nearcore 2.14.0 removed the DelegateV2 action, near-api-js 7 dropped keyStores and WalletConnection, and Pagoda's RPC is shut down. On 3 November, 19 of the 67 hackathon projects with a public repository used something NEAR deprecated, removed or changed.
NEARpedia is a live knowledge layer for those agents: an MCP server with 27 tools and a REST API, free and without a key. check_code reads a JS/TS or Rust file, Cargo.toml or package.json and names each stale line with its replacement and source. The list behind it, 136 entries, is built from archived repositories, README notices, npm and crates.io flags, release-note removals and the docs' own markers. The same index answers on protocol upgrades, House of Stake votes, incidents, the NEAR Catalog and partner docs, each answer with a source and a date. A GitHub Action comments on pull requests with stale NEAR code.
On NEAR Agent Market, the NEARpedia Migrator takes a GitHub repository and returns a report and a patch. Each change comes from a model in a TEE on NEAR AI Cloud and is kept only if it parses, uses names near-api-js 7 exports, passes RPC params in the shape NEAR's RPC reference gives, and leaves fewer findings. Try it on github.com/UnityNodes/near-stale-demo.
NEAR's role: protocol state and the validators' upgrade vote are read from mainnet RPC every 15 minutes; House of Stake proposals come from vote.dao and venear.dao; /ask answers through a TEE model on NEAR AI Cloud with a signature anyone can verify; the migrator is hired and paid on NEAR Agent Market; and a Rust contract on mainnet, on an account with no keys left, keeps one hash of the database per day, so anyone can check which data an answer came from.
Live: https://near-pedia.xyz