# Doma Marketplace

<figure><img src="/files/MyW3m3PBt4eQBdu3GyUe" alt=""><figcaption></figcaption></figure>

Doma Marketplace is provided to simplify trading of tokenized names on-chain. It has following components:

* [Orderbook Rest API](/api-reference/orderbook-api.md) for on-chain trading using [SeaPort protocol](https://github.com/ProjectOpenSea/seaport).
* [Poll API](/api-reference/poll-api.md) for marketplace-related events.
* Marketplace-related data (listings, offers) in [Doma Subgraph](/api-reference/doma-multi-chain-subgraph.md).
* Syndicated listings and offers from external marketplaces (OpenSea).
* [`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk) to simplify integrations of Doma Marketplace.

### How to Use Orderbook API

* It's highly recommended to use [`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk) to interact with [Orderbook API](/api-reference/orderbook-api.md), since it abstracts underlying complexities of working with Seaport Protocol, granting on-chain approvals, and computing fees.
* When not using [`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk), [`seaport-js`](https://github.com/ProjectOpenSea/seaport-js) library is recommended (which is used by SDK under the hood).

### Marketplace Fees

Doma Orderbook API enforces inclusion of following fees into consideration items:

* Doma Protocol Fee
  * Receiver Address:
    * Testnet: `0x2E7cC63800e77BB8c662c45Ef33D1cCc23861532`
    * Mainnet: `0x5f1F2b4ad2E3a7587276B226c9B58Cb9227177bB`
  * Percentag&#x65;*: 0.5%*
* Name Token Royalties. Can be fetched by calling [`royaltyInfo`](https://eips.ethereum.org/EIPS/eip-2981) method on an [Ownership Token Smart contract](/api-reference/doma-smart-contracts-api.md#ownership-token-contract).
* OpenSea Fee (only when creating a listing/offer on OpenSea orderbook). Collection fee value can be fetched using [Get Collection API](https://docs.opensea.io/reference/get_collection) (required fee values from response should be included).
  * Since OpenSea API will also include royalty items, they should be filtered out to prevent double inclusion into considerations.

To simplify fees calculation, [Fee Information API](/api-reference/orderbook-api.md#get-v1-orderbook-fee-orderbook-chainid-contractaddress) is provided.

{% hint style="success" %}
When using [`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk), fees are calculated automatically.
{% endhint %}

### Supported Currencies

Supported currencies can be fetched programmatically using [Currencies API](/api-reference/orderbook-api.md#get-v1-orderbook-currencies-chainid-contractaddress-orderbook).

{% hint style="success" %}
[`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk) provides a helper [`getSupportedCurrencies`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk#user-content-get-supported-currencies) method, which returns list of all supported currencies.
{% endhint %}

### Making ETH Offers

Since SeaPort doesn't support making offers in ETH (as it's a native gas token, not an ERC-20), ETH should be wrapped to wETH using a wrapper contract. Supported wrapper contract addresses can be obtained using [Currencies API](/api-reference/orderbook-api.md#get-v1-orderbook-currencies-chainid-contractaddress-orderbook) - wrapper contracts have a `nativeWrapper` flag set in the response.

{% hint style="success" %}
When using [`@doma-protocol/orderbook-sdk`](https://www.npmjs.com/package/@doma-protocol/orderbook-sdk), wrapping is performed automatically.
{% 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://docs.doma.xyz/doma-marketplace.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.