> 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/developers/introduction/what-is-carbon.md).

# What is Carbon

What Carbon is for API users: an RFQ venue built on SYMM where solvers quote your trades, settled on Arbitrum, with crypto and tradfi account modes.

Carbon is a **non-custodial perpetual-futures platform** built on the [SYMM](https://www.symm.io/) protocol. The Carbon Trading API is its programmatic surface: a REST API to trade, manage positions, and read market data without touching a smart contract directly. You keep custody of your funds.

### The RFQ model

Most exchanges run a Central Limit Order Book (CLOB): your order matches against another anonymous order. Carbon is an **RFQ (Request for Quote)** venue:

1. You (the **trader**, `PartyA`) submit an intent — "go long 1 BTC at 10×."
2. A **solver** (the counterparty, `PartyB`) — a professional market maker — prices it and takes the other side.
3. The trade **settles on-chain on Arbitrum**, collateralized by both sides.

There's no shared book you match into; your counterparty is always a solver that quoted your trade. That's why the API has a `solver` parameter and `/v1/solvers/...` endpoints reporting each solver's liquidity and funding.

### Where trades settle

Carbon settles on **Arbitrum** (chain ID `42161`). Every account and market request carries a `chainId` identifying the deployment.

### Two account modes: crypto and tradfi

| Mode       | Margin model                                     | Positions         |
| ---------- | ------------------------------------------------ | ----------------- |
| **Crypto** | **Cross** (default) or **isolated** per position | Cross or isolated |
| **TradFi** | **Isolated** — each position has its own margin  | Isolated only     |

Crypto positions are cross unless you pass `isolate: true`; tradfi positions are always isolated. See [Accounts & trading modes](https://docs.carbon.inc/developers/architecture/accounts-and-trading-modes.md).

### Markets

* **Crypto perps** — BTC, ETH, and the long tail of crypto assets.
* **RWA (Real-World Assets)** — tokenized equities and commodities, priced from traditional-market feeds with market-hours schedules, under `/v1/rwa/...`.

### What the API gives you

* **Authenticate** a wallet and mint scoped API keys.
* **Manage accounts** — subaccounts, balances, equity.
* **Trade** — open/close, add/remove margin, TP/SL, and batches.
* **Read** — live positions, order & funding history, prices, markets, solver data.


---

# 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/developers/introduction/what-is-carbon.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.
