> 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/jp/kaihatsu/kihon/chiliz-chain-setsuzoku.md).

# Chiliz Chain に接続する

public RPC endpoint（HTTP/WebSocket）を介して、または独自の node を実行して、Chiliz Chain Mainnet または Spicy Testnet に接続します。

プロジェクトを Chiliz Chain に接続するには、2つの方法があります。

* RPC endpoint を使用する -- Mainnet または Testnet。
* 独自の Chiliz Chain node を実行する。

RPC endpoint を使用すると、HTTP または websocket を介して node と直接やり取りできます。

{% content-ref url="/pages/TZOWEML9LNrjmzVZQ1aQ" %}
[RPC で接続する](/jp/kaihatsu/kihon/chiliz-chain-setsuzoku/rpc-setsuzoku.md)
{% endcontent-ref %}

独自の Chiliz Chain node を実行することもできます。これにより、より高度な制御とプライバシーが得られますが、より高い技術力とリソースが必要になります。

{% content-ref url="/pages/RRrihAgbP5zCrOY7AtuZ" %}
[Chiliz Chain Node を実行する](/jp/kaihatsu/kihon/chiliz-chain-setsuzoku/node-jikko.md)
{% endcontent-ref %}

あなたが Chiliz Chain Validator の場合、独自の validator node を実行する方法については、こちらのガイドをご覧ください。

{% content-ref url="/pages/etaoGv2HbpZfs4wjUB0I" %}
[Validator node の運営](/jp/gakushu/validator/validator-node-unei.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 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/jp/kaihatsu/kihon/chiliz-chain-setsuzoku.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 `automate deployments from our CI pipeline` 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.