Skip to main content
The Rust crate meerkat-mobkit is the primary interface for MobKit. All other interfaces (JSON-RPC, SDKs, console) are built on top of it.

Installation

Cargo.toml

Quick start

Core types

MobKitConfig

Top-level configuration for the module runtime.

ModuleConfig

Configuration for a single module.

EventEnvelope

Timestamped event wrapper.

UnifiedEvent

Agent or module event discriminator.

Runtime functions

start_mobkit_runtime

Bootstrap a module-only runtime:

start_mobkit_runtime_with_options

Bootstrap with additional options:

UnifiedRuntime::builder

Builder for the combined mob + module runtime:
For identity-first runtimes with a roster provider, the Rust builder can enable identity-scoped agent memory injection. Use the bundled markdown store with persistent_state:
The bundled provider stores records under <persistent_state>/agent-memory/<realm>/<identity>.md, recalls contextually by default, injects matching records into the next identity-first send, and also injects during materialize/resume/respawn/reset. To supply your own storage or retrieval authority, pass an Arc<dyn AgentMemoryProvider> with .agent_memory(provider, config). Rust callers can write, read, and delete durable records through the unified runtime:

Module routing

route_module_call

Route a call to a module:

route_module_call_rpc_json

Route via JSON-RPC:

Operational subsystem functions

Scheduling

Decisions

Authentication

Governance

HTTP routers

Build Axum routers for serving the console and interactions:

See also