What problem does it solve? Developers struggle to understand how the x402 protocol turns the HTTP 402 status code into a machine-readable payment flow on Algorand, including how the client, resource server, and facilitator components interact and how Algorand-specific features like fee abstraction and ASA payments work. ## Core Features & Use Cases - Protocol Explanation: Teaches the full HTTP 402 payment flow, from initial request through X-PAYMENT header retry to on-chain settlement, with sequence diagrams. - Component Architecture: Details the three components (client, resource server, facilitator) and their TypeScript and Python package ecosystems such as @x402-avm/express and x402-avm[fastapi]. - Algorand-Specific Guidance: Covers CAIP-2 network identifiers, fee abstraction via atomic transaction groups, ASA/USDC support, and common troubleshooting errors. - Use Case: A developer asks "how does x402 work with Algorand" and receives a structured walkthrough of the payment flow, package installation commands, environment variable setup, and scheme registration code. ## Quick Start Ask the assistant to explain how the x402 payment protocol works with Algorand and walk through the client, server, and facilitator roles.