# Implementation strategy

At a high level, there are four different and distinct ways marketplaces can integrate with Winter!&#x20;

1. [Directly with smart contracts](/marketplace-integrations/implementation-strategy/directly-with-smart-contracts.md) (hardest!)
2. [Aggregation APIs](/marketplace-integrations/implementation-strategy/aggregation-apis.md) (e.g. Reservoir) (easiest!)
3. [Winter can call your APIs to build a transaction](/marketplace-integrations/implementation-strategy/apis-to-build-a-transaction.md)
4. [Winter can call your APIs to both build and submit a transaction](/marketplace-integrations/implementation-strategy/build-and-submit-a-transaction.md)

🚧 Coming soon - a self serve dashboard for you to integrate on your own!

For all implementation strategies, we require some type of API like `getNFTDetails` that returns:

1. NFT metadata (name, image, tokenId, etc)
2. NFT order data
3. Listing status (e.g. available, sold, etc)
4. NFT type (e.g. 721 vs 1155)
5. Seller details (e.g. wallet address)


---

# 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.usewinter.com/marketplace-integrations/implementation-strategy.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.
