# Auto-Match

<figure><img src="https://3259001724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6y0CGU3zxwDmKqf6UMQ6%2Fuploads%2FvkO01p7KozfNbRpF50PX%2FAuto%20match%20(2).png?alt=media&#x26;token=a26360ba-b218-4167-b34d-39927f947460" alt=""><figcaption></figcaption></figure>

Auto-Match, in a nutshell, searches for existing orders that meet or exceed initial order criteria, then auto-fills the matches prior to creating the initial order.

When executing the order, your order will be created with any remaining tokens after the Auto-Matching took place.

## Example

Two orders already exist on OTSea. These orders are open and unfilled. The orders are:

Order A: Selling 1000 $OTSEA for .01 ETH

Order B: Selling 2000 $OTSEA for .03 ETH

**Blockto A then wants to buy 100 $OTSEA tokens for .1 ETH**, so they head to the order creation page to input the order. During the process, the system locates the two orders that are already open and are at a better price than their order. Assuming Blockto A confirms the Auto-Match of both orders, the order creation process will look like the following:

Order initiated, offering .1 ETH for 100 $OTSEA \[0.001 ETH per token]

**Auto-Match #1:** Buy 1000 $OTSEA for .01 ETH from **Order A** \[0.00001 ETH per token]

**Auto-Match #2:** Buy 2000 $OTSEA for .03 ETH from **Order B** \[0.000015 ETH per token]

**Create Order With Remainder:** Sell .06 ETH for 60 $OTSEA&#x20;

The result here is that Blockto A received many more tokens than they were initially seeking, since the system identified orders at a better price that they were not aware of.

Auto-Match operates as a hybrid order book, that fits into the existing order system of OTSea. Users can always choose whether to create orders with or without Auto-Matched orders, though the frontend will always present the user with Auto-Match orders that are at an equal or better price than they requested.

Auto-Match is available on all chains.


---

# 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://otsea.gitbook.io/otsea/features/auto-match.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.
