# Manual Token ID Bidding

## Feature Overview

* [x] Support [Magic Eden ETH](/nft-butler/features/magic-eden-token-bidding.md) & [Ordinals Bidding Task](/nft-butler/features/ordinals-token-bidding.md)
* [x] Bidding by Token IDs on [Base](/nft-butler/features/base-bidding.md) Chain
* [x] Bidding by Token IDs on [Ape](/nft-butler/features/ape-chain-bidding.md) Chain
* [x] Bidding by Token IDs on [Arbitrum](/nft-butler/features/arbitrum-bidding.md) Chain
* [x] Bidding by Token IDs on [Bera](/nft-butler/features/bera-bidding.md) Chain
* [x] Bidding by Token IDs on [Abstract](/nft-butler/features/abstract-bidding.md) Chain
* [x] Bidding by Token IDs on [Ronin](/nft-butler/features/ronin-bidding.md) Chain
* [x] Bidding by Token IDs on [HyperEVM](/nft-butler/features/hyperliquid-bidding.md) Chain
* [x] Bidding by Token IDs on [Monad](/nft-butler/features/monad-bidding.md) Chain
* [x] Bidding by Token IDs for ERC721 & ERC1155 Tokens
* [x] Bidding on ENS Token IDs
* [x] Excluding ownder addresses for ERC721 while bidding
* [x] Support for [Auto Listing configuration](/nft-butler/features/bidding-and-autolisting.md) to automate full flip roundtrip
* [x] Supporting safety features like Floor Price caps & Asset Limits

## Creating a Task

By clicking on the **Create Manual Task** Button on your token task list you'll be able to bid on any collection by copying the collection link / slug into Butler (no indexing required). You can also configure token ID ranges manually

<figure><img src="/files/wKqsjb83RfTCIJjWqOfs" alt=""><figcaption><p>Create a manual token bidding task</p></figcaption></figure>

* Multiple token ids can be specified when separating them with comma `,`
* The token id is always the last number on the Opensea link to an NFT. It's usually a number between 1 and 10'000 but can also be a very long number like this one:\
  \
  Link: [https://opensea.io/assets/ethereum/0x495f947276749ce646f68ac8c248420045cb7b5e/**42745998150656004690816543961586238000273307462307754421658803578179357246440**](https://opensea.io/assets/ethereum/0x495f947276749ce646f68ac8c248420045cb7b5e/42745998150656004690816543961586238000273307462307754421658803578179357246440)\
  \
  Smart contract: 0x495f947276749ce646f68ac8c248420045cb7b5e\
  \
  Token ID: **42745998150656004690816543961586238000273307462307754421658803578179357246440**
* The "Smart contract addr" field is optional but can be used to bid on collections with shared contract address such as the OpenSea Storefront contract or Art Block collections
* Butler does also support **ERC-1155 tokens** for bidding

<figure><img src="/files/ic256PXzoXa1C05rPyZA" alt=""><figcaption><p>Creating a manual token bidding task for a specific ERC-1155 Token (The NFT Butler Lifetime license!)</p></figcaption></figure>

* You can also use the [**#community-bot**](/nft-butler/products-and-services/discord-bot.md) in our Discord server to [**/scan**](/nft-butler/products-and-services/discord-bot/scan.md) an entire collection and get a useful output of all token ids per traits or assets

<figure><img src="/files/rAR7meVvTIaYnyLGPqKG" alt=""><figcaption><p>/scan a collection</p></figcaption></figure>

* Here you can also find some more info about the [/scan](/nft-butler/products-and-services/discord-bot/scan.md) **output** and how to deal with it:\
  <https://www.youtube.com/watch?v=CkkvwqkKelU>
* And if you would like to use the search engine you can simply [**/add**](/nft-butler/products-and-services/discord-bot/add.md) new collections on the #community-bot too.

<figure><img src="/files/spI0rstNaKJ2C5XsC4zV" alt=""><figcaption><p>Adding a new Collection to the Butler Search engine</p></figcaption></figure>

## ENS Token bidding

ENS Token bidding works the same as manual bidding. You'll basically have to define the token ids to bid on. However the #community-bot can help you to find those token ids with the [**/ens** ](/nft-butler/products-and-services/discord-bot/ens.md)command.

* It can be used to generate token ids for nummeric ENS tokens such as 0001.eth - 1000.eth:<br>

  <figure><img src="/files/SMGwidFxqvs1SUcTpewr" alt=""><figcaption><p>generate ens token ids 0001.eth - 1000.eth</p></figcaption></figure>
* ENS Token IDs can also be generated for strings such as 'casino.eth' and others (comma-separated):

<figure><img src="/files/nH7uQLuggpp7oQWrIe6w" alt=""><figcaption><p>generate ens Token IDs</p></figcaption></figure>

There are two different ENS smart contracts:

```
    "contracts": [
        {
            "address": "0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85",
            "chain": "ethereum",
            "token_standard": "erc721"
        },
        {
            "address": "0xd4416b13d2b3a9abae7acd5d6c2bbdbe25686401",
            "chain": "ethereum",
            "token_standard": "erc1155"
        }
    ],
```

* Make sure to add the right contract to your task config to make sure it will find it's bidding target. The current implementation of our [Discord bot ](/nft-butler/products-and-services/discord-bot/ens.md)will let you choose if you want to generate token ids for the ERC721 contract or the ERC1155 Contract version.

{% hint style="info" %}
You can check the ENS Token ID by replacing the token id (and contract) on an OpenSea Link at the very end:\
\&#xNAN;*[https://opensea.io/assets/ethereum/\<contract>/\<tokenid](https://opensea.io/assets/ethereum/<contract>/<tokenid)>*

Example for **0001.eth** below:
{% endhint %}

{% embed url="<https://opensea.io/assets/ethereum/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/38764329101403256878217503524140705778209985981144907919668889447405219871633>" %}


---

# 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.nftbutler.io/nft-butler/task-types/manual-token-id-bidding.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.