# API Overview

Bound provides a B2B API suite for programmatic access to the trading infrastructure and derivatives marketplace.

## Authentication

All protected endpoints use **JWT Bearer tokens**, obtained by authenticating with a BIP322 Bitcoin signature.

```http
Authorization: Bearer <access_token>
```

**Token lifetimes:**

* Access token: **10 minutes**
* Refresh token: **7 days**

## Endpoint groups

| Group             | Description                              |
| ----------------- | ---------------------------------------- |
| `auth`            | Authentication and token management      |
| `wallets`         | Create and manage trading wallets        |
| `transactions`    | Create, sign, and broadcast transactions |
| `pools`           | Pool data and management                 |
| `tokens`          | Token listings and details               |
| `positions`       | LP position data                         |
| `histories`       | Trade history                            |
| `etch`            | Rune etching and Virtual Mint            |
| `vm-transactions` | Virtual Mint transactions                |
| `diamond-hand`    | Diamond Hands rewards                    |
| `sodax`           | SODAX crosschain transactions            |
| `activity-feed`   | Unified activity feed                    |
| `refund`          | Refund requests                          |
| `event-source`    | Server-Sent Events (SSE)                 |

{% hint style="info" %}
**VERIFY** - Base URLs for production and staging environments, rate limits, and testnet availability to be confirmed with team.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://bound-1.gitbook.io/bound-docs/developer-guide/api-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.