> For the complete documentation index, see [llms.txt](https://docs.bitbond.com/asset-tokenization-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitbond.com/asset-tokenization-suite/overview.md). # Overview Bitbond builds the tokenization stack used by banks, asset managers, and corporate issuers to bring real-world assets on-chain. These docs cover everything you need to ship with our two products. Where to start [**Token Tool**](/asset-tokenization-suite/token-tool/intro-token-tool.md) – a no-code studio for deploying compliant tokens, running on-chain token sales, locking supply, automating payments, and managing NFTs across 11+ chains. Best for teams who want to launch a token quickly or programmatically through the [Token Tool API](/asset-tokenization-suite/token-tool/token-tool-api.md). [**Offering Manager**](/asset-tokenization-suite/offering-manager/intro-offering-manager.md) – the end-to-end primary issuance platform: investor onboarding, KYC, multi-payment rails, a white-label invest page, order and allocation management, and post-issuance servicing. Best for teams running a full offering with regulated distribution partners. If you're not sure which one fits, [contact us](https://www.bitbond.com/contact-us) and we'll point you at the right product. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bitbond.com/asset-tokenization-suite/overview.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 `build a script that syncs our docs to a CMS` 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.