> For the complete documentation index, see [llms.txt](https://docs.mav.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mav.xyz/technical-reference/maverick-v2/v2-contracts/maverick-v2-supplemental-contracts/routerbase/pushoperations.md).

# PushOperations

**Inherits:** [Payment](/technical-reference/maverick-v2/v2-contracts/maverick-v2-supplemental-contracts/paymentbase/payment.md), [IPushOperations](/technical-reference/maverick-v2/v2-contracts/maverick-v2-supplemental-contracts/routerbase/ipushoperations.md)

Exactinput router operations that can be performed by pushing assets to the pool to swap.

### Functions <a href="#functions" id="functions"></a>

#### exactInputSinglePackedArgs <a href="#exactinputsinglepackedargs" id="exactinputsinglepackedargs"></a>

Perform an exact input single swap with compressed input values.

```solidity
function exactInputSinglePackedArgs(bytes memory argsPacked) public payable returns (uint256 amountOut);
```

#### exactInputSingle <a href="#exactinputsingle" id="exactinputsingle"></a>

Perform an exact input single swap without tick limit check.

```solidity
function exactInputSingle(
    address recipient,
    IMaverickV2Pool pool,
    bool tokenAIn,
    uint256 amountIn,
    uint256 amountOutMinimum
) public payable returns (uint256 amountOut);
```

**Parameters**

| Name               | Type              | Description                                                            |
| ------------------ | ----------------- | ---------------------------------------------------------------------- |
| `recipient`        | `address`         | The address of the recipient.                                          |
| `pool`             | `IMaverickV2Pool` | The Maverick V2 pool to swap with.                                     |
| `tokenAIn`         | `bool`            | True is tokenA is the input token. False is tokenB is the input token. |
| `amountIn`         | `uint256`         | The amount of input tokens.                                            |
| `amountOutMinimum` | `uint256`         | The minimum amount of output tokens expected.                          |

#### exactInputMultiHop <a href="#exactinputmultihop" id="exactinputmultihop"></a>

Perform an exact input multi-hop swap.

```solidity
function exactInputMultiHop(address recipient, bytes memory path, uint256 amountIn, uint256 amountOutMinimum)
    external
    payable
    returns (uint256 amountOut);
```

**Parameters**

| Name               | Type      | Description                                   |
| ------------------ | --------- | --------------------------------------------- |
| `recipient`        | `address` | The address of the recipient.                 |
| `path`             | `bytes`   | The path of tokens to swap.                   |
| `amountIn`         | `uint256` | The amount of input tokens.                   |
| `amountOutMinimum` | `uint256` | The minimum amount of output tokens expected. |

<br>


---

# 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.mav.xyz/technical-reference/maverick-v2/v2-contracts/maverick-v2-supplemental-contracts/routerbase/pushoperations.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.