# Network Endpoints

<figure><img src="https://2372007595-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Tecsoe4KNURIiIXeVdO%2Fuploads%2Fjb3gHNUGCy6g25ZYKoBf%2FNetwork%20Endpoints.png?alt=media&#x26;token=0868f82d-afcf-4863-a0e3-2c902a0a9fe0" alt=""><figcaption></figcaption></figure>

This index guide contains network details for the KCC Mainnet and KCC Testnet and lists their associated RPC and node endpoints.

## KCC Mainnet

The native token of the KCC Mainnet is KCS and is used for gas.

<table><thead><tr><th width="223" align="center">Properties</th><th width="554" align="center">Network Details</th></tr></thead><tbody><tr><td align="center">NetworkName</td><td align="center">KCC Mainnet</td></tr><tr><td align="center">ChainID</td><td align="center">321</td></tr><tr><td align="center">Gas Token</td><td align="center">KCS</td></tr><tr><td align="center">Faucet</td><td align="center"><a href="https://faucet.kcc.io/">https://faucet.kcc.io/</a></td></tr><tr><td align="center">RPC Endpoint</td><td align="center"><a href="https://rpc-mainnet.kcc.network">https://rpc-mainnet.kcc.network</a><br>or<br><a href="https://kcc-rpc.com">https://kcc-rpc.com</a></td></tr><tr><td align="center">Web Socket Endpoint</td><td align="center">wss://rpc-ws-mainnet.kcc.network<br>or<br>wss://ws.kcc-rpc.com</td></tr><tr><td align="center">Block Explorer</td><td align="center"><a href="https://explorer.kcc.io/en">https://explorer.kcc.io/en</a> or <a href="https://scan.kcc.io/">https://scan.kcc.io/</a></td></tr></tbody></table>

## KCC Testnet

<table><thead><tr><th width="213" align="center">Properties</th><th align="center">Network Details</th></tr></thead><tbody><tr><td align="center">NetworkName</td><td align="center">KCC Testnet</td></tr><tr><td align="center">ChainID</td><td align="center">322</td></tr><tr><td align="center">Gas Token</td><td align="center">KCS</td></tr><tr><td align="center">Faucet</td><td align="center"><a href="https://faucet-testnet.kcc.network/">https://faucet-testnet.kcc.network/</a></td></tr><tr><td align="center">RPC Endpoint</td><td align="center"><a href="https://rpc-testnet.kcc.network">https://rpc-testnet.kcc.network</a></td></tr><tr><td align="center">Web Socket Endpoint</td><td align="center">wss://rpc-ws-testnet.kcc.network</td></tr><tr><td align="center">Block Explorer</td><td align="center"><a href="https://scan-testnet.kcc.network">https://scan-testnet.kcc.network</a></td></tr></tbody></table>

## Infrastructure Providers <a href="#infrastructure-providers" id="infrastructure-providers"></a>

Public RPCs may have traffic or rate-limits depending on usage. You can sign up for a dedicated free RPC URL at the following:

* [Getblock](https://getblock.io/en/)
* [BlockPI](https://chains.blockpi.io/#/polygon)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kcc.io/developers/network-endpoints.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
