> For the complete documentation index, see [llms.txt](https://bso-wiki.oldschool.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bso-wiki.oldschool.gg/custom-items/item-contracts.md). # Item Contracts Item contracts work similar to Farming contracts, the bot will ask you for a random item, and you hand it in for a reward. You get GP, clue scrolls, XP Lamps, dragon and rune items as rewards. You can get your first item contract using `/ic info`. This is also how you check your current contract. To hand in your item contract, use /`ic send`. When you do this you will see the rewards, your next contract, your current streak and total completed. There is an 8 hour cooldown for handing in item contracts. * You can be assigned any item that's dropped by TMB's or UMB's * You build up a streak if you don't skip any contracts, reaching certain divisible milestones in your streak grants you an extra reward. Every 10th, 25th, 50th, 100th contract gets you a bonus reward, proportional to the size of the streak. It pays to not skip! * Item contracts can be skipped with `/ic skip`, however this will reset your streak and incur a 4 hour cooldown. * You can buy the assigned item off other players, you don't have to obtain it yourself. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://bso-wiki.oldschool.gg/custom-items/item-contracts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.