> For the complete documentation index, see [llms.txt](https://docs.carbon.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carbon.inc/how-carbon-works.md).

# How Carbon Works

- [Carbon Solution & Architecture Overview](https://docs.carbon.inc/how-carbon-works/carbon-solution-and-architecture-overview.md): How Carbon's two solver tracks share one Automated RFQ (ARFQ) layer: off-chain quote streaming, on-chain commitment, solver hedging and settlement.
- [Solver Network Explained](https://docs.carbon.inc/how-carbon-works/solver-network-explained.md): How third-party solvers on Carbon's crypto perpetual track deposit collateral, stream quotes, hedge filled trades and keep margin on and off chain.
- [Counterparty Risk](https://docs.carbon.inc/how-carbon-works/counterparty-risk.md): How counterparty risk works on Carbon: each trade is a bilateral contract with a solver, collateral is locked on-chain by both sides, and liquidators can close either.
- [Carbon Solver (CLP)](https://docs.carbon.inc/how-carbon-works/carbon-solver-clp.md): What the Carbon Solver and its CLP vault are, how USDC depositors earn from Carbon TradFi flow, the vault's risks, its contract address and audits.


---

# 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.carbon.inc/how-carbon-works.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.
