> For the complete documentation index, see [llms.txt](https://docs.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybit.com/start.md). # Getting Started - [Documentation Overview](https://docs.trybit.com/start/overview.md): The purpose of this documentation is to show how to integrate any project with Trybit and start accepting cryptocurrency payments. - [How the Integration Works](https://docs.trybit.com/start/how-it-works.md) - [Integration Testing](https://docs.trybit.com/start/test-integration.md) - [How to Get API Keys](https://docs.trybit.com/start/get-api-keys.md) - [SDK for Work with API](https://docs.trybit.com/start/sdk.md) - [Integration of Icons and Buttons](https://docs.trybit.com/start/payment-icons-buttons.md): Proper use of branded elements helps create a unified and recognizable user experience and increases conversion rates during the payment selection process. - [Support and FAQ](https://docs.trybit.com/start/support-faq.md): Answers to frequent technical questions about integration and Trybit support contacts. --- # 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://docs.trybit.com/start.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.