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

# Inverse Prices

Sidepit's native price is the amount of Bitcoin paid for one U.S. dollar, expressed as integer satoshis per USD.

`USD/BTC = 100,000,000 ÷ sats-per-USD`

| Sats per USD | Familiar USD per BTC |
| -----------: | -------------------: |
|        1,000 |             $100,000 |
|        1,250 |              $80,000 |
|        2,000 |              $50,000 |

The directions move opposite each other:

* a higher Sidepit price means a lower familiar USD/BTC price;
* a lower Sidepit price means a higher familiar USD/BTC price; and
* a Sidepit bar high is the familiar USD/BTC low for the same interval.

## Linear satoshi P\&L

For one contract, a one-tick move changes P\&L by the contract's published `tic_value` in sats. If `unit_size` is $500 and the minimum tick is one sat per USD, one tick is worth 500 sats per contract.

Convert to familiar USD/BTC at the display edge. Keep order construction, matching, margin, and P\&L reasoning in the exchange's native integer units to avoid double inversion or floating-point rounding.


---

# 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.sidepit.com/use-sidepit/beta/trading/inverse.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.