> For the complete documentation index, see [llms.txt](https://docs.put.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.put.com/developers/clients/rust-api.md). # Rust API Rust API PUT's Rust crates are published to crates.io and can be found on docs.rs with the "put-" prefix. Some important crates: * put-program — Imported by programs running on PUT, compiled to BPF. This crate contains many fundamental data types and is re-exported from put-sdk, which cannot be imported from a PUT program. * put-sdk — The basic off-chain SDK, it re-exports put-program and adds more APIs on top of that. Most PUT programs that do not run on-chain will import this. * put-client — For interacting with a PUT node via the JSON RPC API.put-cli-config — Loading and saving the PUT CLI configuration file. * put-clap-utils — Routines for setting up a CLI, using clap, as used by the main PUT CLI. Includes functions for loading all types of signers supported by the CLI. --- # 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.put.com/developers/clients/rust-api.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.