> For the complete documentation index, see [llms.txt](https://docs.stonkfun.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonkfun.bot/transaction-flow/review.md). # Review Once STONKFUNBOT understands what you're asking for, it prices the real action and shows you a proposal — before anything is signed. ## What a proposal contains * The exact terms of the action (what's being launched or swapped, and against what). * The real, live-quoted cost — read at request time, not estimated or assumed. * A short code you'll use to confirm it. * How long the proposal stays open. ## Why this step exists Costs on STONKFUNBOT aren't fixed — a launch's real price comes from the launchpad at request time, and a swap's price depends on live market conditions. Review is where that real number gets computed and shown to you, so your confirmation in the next step is informed consent to a specific, known cost rather than a blank check. Nothing is signed at this point. A proposal is not a launch, and a quote is not a swap. ## Next [Confirm](/transaction-flow/confirm.md) that specific proposal, or let it expire and ask again if anything about it should change. --- # 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.stonkfun.bot/transaction-flow/review.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.