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

# Merging & Splitting Shares

Convert between USDC and YES / NO share pairs directly.

Prediction markets have two primitives that don't exist in traditional trading: **Split** and **Merge**. They let you convert directly between USDC and matched pairs of YES + NO shares, without going through the order book.

{% hint style="info" %}
Split and Merge are executed by the protocol, not against other users — no bid-ask spread and no impact on market price. Useful when the book is thin or the spread is wide.
{% endhint %}

## The Core Identity

For every market:

> **1 YES share + 1 NO share = $1.00 USDC**

Exactly one side will ultimately redeem for $1.00 and the other for $0, so holding both is guaranteed to be worth $1.00 at resolution. The protocol lets you convert between them right now.

## Split: USDC → Shares

Lock **$1 USDC** and receive **1 YES + 1 NO** share.

<figure><picture><source srcset="/files/FJ0A2bpM5bSN05lV9Vd8" media="(prefers-color-scheme: dark)"><img src="https://2587188963-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZpNZvaCzAbpqVCg9WNwK%2Fuploads%2Fgit-blob-7872d5179ec1d6894ba7d28f37a43f414f4aa2d8%2Ftrading_merging-and-splitting_1.svg?alt=media" alt=""></picture><figcaption></figcaption></figure>

**Account changes:** USDC ↓ by the amount split; YES and NO balances both ↑ by the same amount.

### When to Use

* **Short** an outcome — split, then sell the side you don't want
* **Accumulate inventory** without paying the spread
* **Express a nuanced view** by holding a different YES / NO ratio than the market implies

> Your all-in cost is $1 per pair. If you sell one side, the remaining side's effective cost is whatever you didn't recover — e.g. sell NO at 40¢ and your YES effectively costs 60¢.

## Merge: Shares → USDC

Return **1 YES + 1 NO** and receive **$1 USDC** back.

<figure><picture><source srcset="/files/SMVXHZU1brjv2GeprgWx" media="(prefers-color-scheme: dark)"><img src="https://2587188963-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZpNZvaCzAbpqVCg9WNwK%2Fuploads%2Fgit-blob-aafdee99db1a9bc663a66eeb3718d33547fa8791%2Ftrading_merging-and-splitting_2.svg?alt=media" alt=""></picture><figcaption></figcaption></figure>

**Account changes:** YES and NO balances both ↓ by the amount merged; USDC ↑ by the same amount. The amount you can merge is capped by the smaller of your YES and NO balances.

### When to Use

* **Close a hedged position** without paying the spread
* **Lock in the difference** between YES and NO bought at different prices
* **Free up USDC** for another market

## Related

* [Category Markets](/markets-and-trading/category-markets.md) — multi-outcome markets
* [Market Resolution](/fees-and-settlement/market-resolution.md) — how winning shares settle


---

# 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.probly.com/markets-and-trading/merging-and-splitting.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.
