` tag where you want to locate the widget:](#user-content-fn-1)[^1]

<div id="widget"></div>

Add this to the \ ``` [^1]: is this div actually necessary tech-wise? The widget will be displayed as an overlay anyway, right? Why we don't inject it into the body transparently/automatically? [^2]: default customization without showing here if not necessary [^3]: chnage to decimals / name [^4]: is it necessary to add defaultTokenAddress? [^5]: it doesn't explain how I make the widget appear upon clicking on some button. This instruction rather explains how do I display the widget upon page render --- # 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.bitoftrade.com/for-businesses/allpay-widget/quick-start/swap-and-sale-integration.md?ask=&goal= ``` `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.