# Adapter Classification

Every StakeEase adapter can be categorized into one of these four types:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Core Adapters</strong></td><td>Contracts responsible for  StakeEase's efficient working. The <em>Multicall</em> contract is the entry point for any instant (re)staking request. It invokes other adapters in a sequential order to achieve the desired output. The <em>FeeManager</em> contract is used to deduct protocol fees from the user (as an introductory promotion, the fee is currently set to 0 BPS). </td><td></td></tr><tr><td><strong>Fusion Adapters</strong></td><td>Contracts that oversee the execution of StakeEase's Fusion mode. These contracts batch user deposits at the protocol level, i.e., a separate batch is created for users who want to stake into Renzo, and a separate batch is created for users who want to stake into Ether.fi and so on. The fee for the execution of a batch is split across all the participants of that batch.</td><td></td></tr><tr><td><strong>Swap Adapters</strong></td><td><p>Contracts to swap user funds from the deposited asset to the relevant asset (ETH or a LST). </p><p></p><p>For example, if the user provides USDT, <em>OpenOceanAdapter</em> will be used to swap user funds to ETH (or some LST) before proceeding with the rest of the restaking process.</p></td><td></td></tr><tr><td><strong>Stake Adapters</strong></td><td><p>Contracts to handle liquid staking on different applications.</p><p></p><p>For example, <em>LidoAdapter</em> will be used to stake the user's ETH on Lido. </p></td><td></td></tr><tr><td><strong>Restake Adapters</strong></td><td><p>Contracts to handle restaking on different applications.</p><p></p><p>For example, <em>KelpAdapter</em> will be used to stake the user's Liquid Staking Token on Kelp. </p></td><td></td></tr></tbody></table>


---

# 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.stakeease.com/aggregator/technical/adapter-classification.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.