> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/develop/basics/connect-to-chiliz-chain.md).

# Connect to Chiliz Chain

Connect to Chiliz Chain Mainnet or Spicy Testnet via public RPC endpoints (HTTP/WebSocket) or by running your own node.

There are two ways to connect your project to Chiliz Chain:

* Using an RPC endpoint -- Mainnet or Testnet.
* Running your own Chiliz Chain node.

You can use RPC endpoints to interact with a node directly over HTTP or websockets.

{% content-ref url="/pages/oYKKHjOmAZJp2Vfye0kX" %}
[Connect using RPC](/develop/basics/connect-to-chiliz-chain/connect-using-rpc.md)
{% endcontent-ref %}

You can also run your own Chiliz Chain node, which provides greater control and privacy but demands more technical skill and resources.

{% content-ref url="/pages/9YZsEmPaaQYP2h1RqyS1" %}
[Run a Chiliz Chain Node](/develop/basics/connect-to-chiliz-chain/run-a-chiliz-chain-node.md)
{% endcontent-ref %}

If you are a Chiliz Chain Validator, here a guide on how to run your own validator node:

{% content-ref url="/pages/ppcymFdm3NKLps6cECR9" %}
[Running a Validator node](/learn/about-validators/running-a-validator-node.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/develop/basics/connect-to-chiliz-chain.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.