Ideally, one may run their own node when interacting with the Cere Network via Cere Explorer. Another option would be to connect to one of the several public endpoints provided by infrastructure and API service providers.

Network Endpoints

Main Networks

Network URL
Cere Mainnet wss://rpc.mainnet.cere.network/ws

Test Networks

Network URL
Cere Testnet wss://rpc.testnet.cere.network/ws

Example usage with Polkadot-JS API

To connect to the Parity node, use the endpoint in your JavaScript apps like so:

// Using the Polkadot Mainnet Endpoint
const { ApiPromise, WsProvider } = require('@polkadot/api');
async () => {
// Construct a provider with the endpoint URL
  const provider = new WsProvider('wss://rpc.polkadot.io/');
// Create an API instance for Polkadot
  const api = await ApiPromise.create({ provider });
// ...

Third Party Providers

There is currently one third-party provider of RPC infrastructure to the Cere communities, commonly providing access to multiple networks and parachains in a single service. They provide additional services such as higher rate limits, potentially more reliable and scalable service, and additional metrics.

Republic Crypto

Mainnet Archive Node: wss://mainnet.cere-archive.republiccrypto-runtime.com:444