> For the complete documentation index, see [llms.txt](https://robinfun.gitbook.io/robinfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robinfun.gitbook.io/robinfun-docs/disclaimer.md). # disclaimer RobinFun is **experimental software** for launching and trading tokens on a bonding curve. Please read this carefully. * **Not financial advice.** Nothing in this documentation or in the RobinFun app is investment, financial, legal, or tax advice. Do your own research. * **No endorsement.** RobinFun is permissionless — anyone can launch any token. A token appearing on RobinFun is **not** a vetting, endorsement, or guarantee of any kind. * **Tokens are not securities or investments.** Tokens launched on RobinFun are speculative and may have no value. They can go to zero. * **High risk.** Bonding-curve prices can move sharply. Only interact with funds you can afford to lose entirely. * **Smart-contract risk.** Despite testing and verification, smart contracts can contain bugs or be exploited. Interacting with any on-chain contract carries inherent risk. * **Irreversible.** On-chain transactions cannot be undone. Verify addresses, the network (chain `4663`), and amounts before signing. * **Scams.** Only use the official app and the contract addresses listed in this documentation. Be wary of impersonators, fake tokens, and phishing. * **Your responsibility.** You are solely responsible for your decisions, your wallet, and your keys. Comply with the laws and regulations that apply to you. By using RobinFun you acknowledge and accept these risks. --- # 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://robinfun.gitbook.io/robinfun-docs/disclaimer.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.