ProviderLifecycle ProviderRuns ProviderSessions settle_batch grpc_services Rust uses the same protocol and accounting, with its own types and names. Session/run hashes use `B256`; async trait operations return `IntegrationResult`. `ExecutionStream` carries your original JSON output. The application provides `Send + Sync` coverage/execution implementations. Rust · composition signatures pub async fn runtime_from_config( host: HostConfiguration, wallet_operation_path: impl AsRef, coverage: Arc, execution: Arc, ) -> Result pub async fn runtime_from_config_with_options( host: HostConfiguration, wallet_operation_path: impl AsRef, coverage: Arc, execution: Arc, options: RuntimeOptions, ) -> Result Use the retained wallet-operation record. `RuntimeOptions` includes CircleOptions, optional polling interval, runtime limits and hooks; freshness and collection margin come from validated configuration. The helper starts neither the runtime nor a listener. Rust · explicit composition and serving Mppi::new(config: ProviderConfig, chain: Arc, contract: ContractCalls, wallet: Arc, coverage: Arc, execution: Arc) -> Result pub async fn serve(runtime: Arc, listener_config: &ListenerConfig, shutdown: CancellationToken, policy: &ServePolicy) -> Result Trait / method Inputs and result `CoverageProvider::coverage` `&PreparedRequest, &RunContext` → async `IntegrationResult`. Prepare before paid work. `ExecutionProvider::execute` `PreparedRequest, RunContext, Arc, CancellationToken` → `ExecutionStream`. Own termination and reporting. `ProviderRuns::require_coverage` `&RunContext, TokenCounts` → async `IntegrationResult`. Complete remaining bound. `ProviderRuns::report_usage` `&RunContext, TokenCounts` → async `IntegrationResult`. Cumulative counts. `ProviderRuns::report_terminal` `&RunContext, TokenCounts, RunStatus` → async `IntegrationResult`. Definitive final outcome. `ProviderSessions::get / checkpoint` `B256` → async `IntegrationResult`. Inspect or detach history. `ProviderSessions::list` `Option<&str>, usize` → async `IntegrationResult`. Checked cursor/limit. `ProviderSessions::recover` `RecoveryEvidence` → async `IntegrationResult`. No implicit readiness or replay. `ProviderSessions::settle / close` `B256` → async `IntegrationResult`. Inspect state and canonical outcomes. `ProviderSessions::settle_batch` `&[B256]` → async `IntegrationResult`. Ordered item outcomes. `ProviderLifecycle::runs / sessions` No inputs → `Arc`. Integration capabilities. `ProviderLifecycle::grpc_services` No inputs → `GrpcServices`. Register both services. `ProviderLifecycle::discovery` `&str` → `Option`. Publish returned status, headers and bytes. `ProviderLifecycle::start` No inputs → async `IntegrationResult`. Inspect failures. `ProviderLifecycle::shutdown` Absolute `tokio::time::Instant` → async `IntegrationResult`. Retain unresolved work. The Python report/session behavior above also describes protocol obligations in Rust. It does not rename Rust methods: use `settle_batch`, not `settleBatch`. `with_limits` and `with_limits_and_hooks` extend explicit construction with RuntimeLimits and Hooks. Your host owns storage, workers and engine recovery.

MPP-I: Machine Payments Protocol for Inference

Read it with an agent

The paper