> For the complete documentation index, see [llms.txt](https://guide.dem.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dem.exchange/technical/running-a-node/public-api-node.md).

# Public API Node

Most node operators do not expose their API endpoints to the public.

However, if you wish to support the Demex ecosystem in promoting greater decentralization, you may open the relevant ports for your node to the public, and list them on the following open-source **Community API Nodes Listing**:

{% embed url="<https://github.com/Switcheo/carbon-rpc-nodes>" %}

By making your node available on this list, Demex and other dApps are able to advertise your node to users, giving them a broader selection of nodes to connect to as they interact with the protocol.

In the event of downtime by a specific node operator, users can then easily switch to other nodes and continue using dApps without interruption.

When submitting your node to the listing, ensure that your node meets the required hardware requirements, and the node's endpoints are properly configured, by following the [documented prerequisites](https://github.com/Switcheo/carbon-rpc-nodes#prerequisites) closely.


---

# 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://guide.dem.exchange/technical/running-a-node/public-api-node.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.