> For the complete documentation index, see [llms.txt](https://docs.ventuals.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ventuals.com/getting-started/start-trading.md).

# Start Trading

## Enable Trading

To start trading, you'll first need to establish a trading connection, which allows you to place trades without signing each time.

<figure><img src="https://3447241726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXPhlu9j2erMhOQJWJOsI%2Fuploads%2FvdBV6na7FJ8VFVUUSYVE%2Fimage.png?alt=media&amp;token=c23d5143-d540-4720-add1-f8f6705ea5ff" alt=""><figcaption></figcaption></figure>

You will also be asked to sign a builder code fee approval, which is a maximum of 5 bps.

## Ventuals uses USDH

{% hint style="info" %}
USDH is deployed through Stripe's stablecoin platform (Bridge), fully backed 1:1 by US Treasuries, cash, and cash equivalents managed by BlackRock.
{% endhint %}

Markets deployed by Ventuals use USDH as collateral, which is a US dollar-pegged stablecoin.

Other markets which are accessible via the Ventuals app may use USDC as collateral. To trade USDC markets, you'll need a USDC balance. You can easily swap between USDC and USDH using the "Swap Stablecoins" feature.

<figure><img src="https://3447241726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXPhlu9j2erMhOQJWJOsI%2Fuploads%2F6iBVdNPoENFjUNWEVg7a%2Fimage.png?alt=media&amp;token=ec23a799-3d64-4534-b235-6264fefd5c6a" alt=""><figcaption></figcaption></figure>


---

# 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.ventuals.com/getting-started/start-trading.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.
