REMOVED · SERVICE

Pagoda hosted services (RPC, Console, Enhanced API)

Pagoda's hosted RPC endpoints refuse requests and its Console and Enhanced API repositories are archived. docs.near.org's near-api page still uses rpc.testnet.pagoda.co in examples (2026-11-01); use an endpoint from the RPC providers list.

synced 3h agocurated, re-checked on every build

Removed

Use instead: A public RPC endpoint from the providers list (e.g. https://free.rpc.fastnear.com)

Evidence

Repository archivedstrongconfirmed in synced data

https://github.com/near/near-enhanced-api-server (opens in a new tab)

Repository archivedstrongconfirmed in synced data

https://github.com/near/pagoda-console (opens in a new tab)

probemediumchecked by hand 2026-11-01

“HTTP 403 to a JSON-RPC status call (mainnet and testnet endpoints)”

https://rpc.mainnet.pagoda.co (opens in a new tab)

Agents get this entry from check_deprecation("pagoda-services") and GET /api/v1/deprecations/pagoda-services; check_code flags code that uses it. All deprecations →