> For the complete documentation index, see [llms.txt](https://docs.nextblock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nextblock.io/api/examples.md). # Examples Use the examples section based on the transport and level of control you need: * **HTTP**: simplest way to integrate from any language using REST requests * **gRPC**: recommended general-purpose integration if you want the full submission feature set * **QUIC**: lowest-latency submission path for advanced traders sending raw signed transaction bytes * **TX Stream**: separate real-time monitoring service for transaction streams, not a submission API ## Which Path Should You Choose? * Start with **HTTP** if you want the quickest integration and are fine working with JSON requests. * Use **gRPC** if you want language-native clients and support for submission options such as front-running protection, revert-on-fail, disable-retries, and bundle submission. * Use **QUIC** if latency is your top priority and you only need to send raw signed transaction bytes. QUIC does **not** support the extra gRPC submission flags or the batch submission endpoint. * Use **TX Stream** if you want to monitor live transactions for trading or analytics. It uses a different authentication model from the main API. ## Language Sections * [Golang](/api/examples/golang.md) * [Rust](https://github.com/nextblock-ag/nextblock-docs/blob/main/api/examples/rust/README.md) * [Python](/api/examples/python.md) * [JavaScript/TypeScript](/api/examples/javascript.md) * [HTTP](/api/examples/http.md) --- # 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.nextblock.io/api/examples.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.