> 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/developers.md).

# Developers

The **Carbon Trading API** lets you trade perpetual futures on the [SYMM](https://www.symm.io/) RFQ protocol 

Settled on **Arbitrum** over a normal REST API. Authenticate with a wallet, create an API key, and open, close, and manage leveraged positions with plain HTTP. No smart-contract integration or transaction signing on your side.

### Base URL

```
https://gw.carbon.inc/v1
```

All endpoints are versioned under `/v1`. See [Conventions](/developers/http-api/conventions.md) for the request/response contract.

### Documentation

**Introduction**

* [What is Carbon](/developers/introduction/what-is-carbon.md) — the platform and the RFQ model
* [Core concepts & glossary](/developers/introduction/core-concepts-and-glossary.md) — the vocabulary

**Architecture**

* [How trading works](/developers/architecture/how-trading-works.md) — RFQ flow and the submit-then-poll model
* [Accounts & trading modes](/developers/architecture/accounts-and-trading-modes.md) — crypto (cross) vs tradfi (isolated)

**HTTP API**

* [Conventions](/developers/http-api/conventions.md) — base URL, versioning, JSON envelope, units
* [Authentication](/developers/http-api/authentication.md) — session JWTs, API keys
* [Enabling API access](/developers/http-api/enabling-api-access.md) — enable a subaccount and permission a key
* [Errors](/developers/http-api/errors.md) — error envelope, status codes, retries

The full per-endpoint reference is available interactively via Swagger UI at `https://gw.carbon.inc/api`.

### Endpoint families

| Family                 | Base path               | Purpose                                                         |
| ---------------------- | ----------------------- | --------------------------------------------------------------- |
| Account Authentication | `/v1/account-auth/...`  | Enable subaccounts, delegate to API keys, instant-action tokens |
| API Keys               | `/v1/api-keys/...`      | Create, list, rename, revoke keys                               |
| Accounts               | `/v1/accounts/...`      | Subaccounts, balances, isolated virtual accounts                |
| Trade                  | `/v1/trade/...`         | Open, close, cancel, margin, batch operations                   |
| Positions              | `/v1/positions/...`     | Live positions and request-status polling                       |
| TP/SL                  | `/v1/tpsl/...`          | Take-profit / stop-loss                                         |
| Markets                | `/v1/markets/...`       | Market catalog per chain and solver                             |
| Pricing                | `/v1/pricing/...`       | Mark and last/index prices                                      |
| Solvers                | `/v1/solvers/...`       | Per-solver liquidity, caps, funding                             |
| Public Information     | `/v1/public/...`        | Read-only account/position/order/funding queries                |
| Instant Layer          | `/v1/instant-layer/...` | Primitives for fast execution                                   |
| RWA                    | `/v1/rwa/...`           | Real-world-asset tickers and schedules                          |

### In short

1. **Authenticate** your wallet and create an **API key**.
2. **Delegate** trading permissions from a subaccount to that key.
3. **Submit** an order (`POST /v1/trade/create-position`) → get a `tempId`.
4. **Poll** for the result (`GET /v1/positions/open-request/status`).

Your counterparty is always a **solver** that quotes your trade — not an order book. See [What is Carbon](/developers/introduction/what-is-carbon.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carbon.inc/developers/developers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.