Rust SDK

Boundary statement

The Rust SDK has two different integration boundaries: an HTTP client and an optional in-process runtime. Select the feature set deliberately; a client build does not certify an embedded host, and an embedded build does not expose server routes.

Feature modes

Feature	Meaning
http-client	default; async reqwest client and SSE stream support
embedded	links the UAR runtime with host-persistence support
embedded-mobile	adds the runtime's transport-free mobile profile
server	links the runtime's minimal server composition
full	combines HTTP client and server

The HTTP Client exposes typed namespaces for chat, providers, control-plane policy, administration, runs, A2UI, knowledge, ingestion, tools, and embeddings. Its bearer helper attaches the supplied token to requests.

The embedded builder is a host-injection boundary. The host supplies required persistence and, for mobile use, the local inference/provider implementation; the SDK does not silently open a listener or select a remote provider.

Source checkout

Build the independently locked SDK package from the repository root:

cargo check --locked --manifest-path sdks/rust/Cargo.toml
UAR_BASE_URL=http://127.0.0.1:1906 \
  cargo run --locked --manifest-path sdks/rust/Cargo.toml --example chat

Examples cover chat, streaming, tool calls, structured output, embeddings, runs/checkpoints, knowledge CRUD/search, ingestion, and error handling. A network example requires a running, configured UAR server and valid credentials for that server.

Hosted reference

Workspace rustdoc is generated by the documentation deployment and includes the runtime and SDK source APIs. It describes types and methods, not runtime availability or registry provenance.

Registry publication

The manifest names universal-agent-runtime-sdk version 1.0.0. Confirm the crate and exact version on crates.io before using a registry dependency. A pinned source checkout remains the repository-verifiable path when registry availability has not been established.

Profile limits

HTTP-client evidence applies to the exercised minimal or server-full server. embedded-mobile is transport-free and host-supplied. The SDK's server feature selects minimal, not server-full; additive feature builds must be named and checked separately.

Next: Configuration.