> For the complete documentation index, see [llms.txt](https://cluster-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cluster-protocol.gitbook.io/whitepaper/codexero-application-layer/how-codexero-consumes-cluster-infra.md).

# How CodeXero Consumes Cluster Infra

CodeXero is not a standalone product: it is the primary consumption engine for Cluster's infrastructure:

* **Inference**: Every prompt-to-dApp generation calls Cluster's inference API for code generation, planning, and model routing
* **Compute**: Smart contract compilation and deployment verification runs on Cluster compute
* **Data**: Templates and starter repos are sourced through the Cluster ecosystem

Every dApp deployed through CodeXero generates inference token consumption, creating organic demand for the Cluster token at the infrastructure level. CodeXero does not charge separately: all costs are settled at the infra layer.