Rust API#

These pages are generated from the public Rust crates that back the core runtime and adaptive components.

Binding At A Glance#

This summary lists the package identity and support status for the binding.

  • Published crates: nemo-flow and nemo-flow-adaptive

  • Local development paths: crates/core and crates/adaptive

  • Primary audience: Rust consumers who want the native runtime surface directly

The Rust docs are organized by crate because the Rust binding is the source implementation of the runtime. The generated pages mirror each crate’s public module tree.

Main Binding Surfaces#

These entry points are the primary APIs to use from this binding.

  • nemo-flow: core runtime APIs for scopes, tools, LLMs, registries, subscribers, codecs, streams, and observability

  • nemo-flow-adaptive: adaptive runtime helpers, learner implementations, storage backends, and adaptive configuration

Within nemo-flow, most integrations start in api, especially the scope, tool, llm, registry, and subscriber modules. Other important public modules include codec, observability, stream, error, and json.

Within nemo-flow-adaptive, the main surfaces include adaptive configuration, plugin components, storage abstractions, learners, trie-backed data structures, and optional Redis-backed helpers when the feature is enabled.

How To Read The Generated Pages#

Use the crate pages first, then expand into the public modules under each crate:

  • nemo-flow for core runtime behavior

  • nemo-flow-adaptive for adaptive and learning-oriented behavior

That structure matches how Rust consumers import items from the crates.

Use the generated crate entry points when you need symbol-level detail: