AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing tempoxyz/mpp-rs in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewmpp Rust SDK for the **Machine Payments Protocol** MPP lets any client — agents, apps, or humans — pay for any service in the same HTTP request. It standardizes HTTP 402 with an open IETF specification, so servers can charge and clients can pay without API keys, billing accounts, or checkout flows. You can get started today by reading the Rust SDK docs, exploring the protocol overview, or jumping straight to the quickstart. Install Quick Start Server Client Feature Flags | Feature | Description | |---------|-------------| | | Client-side payment providers ( trait, extension) | | | Server-side payment verification ( trait) | | | Tempo blockchain support (includes ) | | | Shared EVM utilities (Address, U256, parsing) | | | reqwest-middleware support with (implies ) | | | Tower middleware for server-side integration | | | Axum extractor support for server-side convenience | | | Hex/random utilities for development and testing | Payment Methods MPP supports multiple payment methods through one protocol — Tempo, Stripe, Lightning, Card, and custom methods. The server advertises which methods it accepts, and the client chooses which one to pay with. This SDK currently implements Tempo (charge and session intents). Protocol Built on the "Payment" HTTP Authentication Scheme, an open specification proposed to the IETF. See mpp.dev/protocol for the full protocol overview, or the IETF specification for the wire format. Contributing Security See for reporting vulnerabilities. License Licensed under either of Apache License, Version 2.0 or MIT License at your option. Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in these crates by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.