> For the complete documentation index, see [llms.txt](https://rwaperp-1.gitbook.io/rwaperp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwaperp-1.gitbook.io/rwaperp-docs/rwaperp-b2b-api.md).

# RWAPerp B2B API

Integrate with RWA Perp through its REST and WebSocket APIs. Start with the quick start, then use the authentication, REST API, WebSocket, and API reference sections as needed.

> Default REST: `https://api-trade.rwaperp.xyz` · VIP REST: `https://api-vip.rwaperp.xyz` (same paths and `RWA-*` signing)\
> **X Layer only** (`chainId = 196`). No other chain is supported.\
> Complete account onboarding first. Then use the trading example with your API credentials. For signing details, see Authentication.

| Section            | Purpose                                                                                  |
| ------------------ | ---------------------------------------------------------------------------------------- |
| Quick start        | Install dependencies and run the trading example                                         |
| Authentication     | Open an account, bind an API key, and sign requests                                      |
| REST API           | Request and response conventions, trading, and withdrawals                               |
| WebSocket          | Public market streams and private account streams                                        |
| REST API reference | Parameters, request bodies, responses, authentication, and rate limits grouped by domain |


---

# 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://rwaperp-1.gitbook.io/rwaperp-docs/rwaperp-b2b-api.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.