What problem does it solve? Building HTTP clients that pay for API access requires manually detecting 402 Payment Required responses, constructing Algorand USDC payment transactions, signing them, and retrying requests with payment headers. This Skill guides you through wiring that entire flow into httpx or requests so payments happen automatically. ## Core Features & Use Cases - Automatic 402 Handling: Wrap httpx (async) or requests (sync) transports so 402 responses trigger payment creation, signing, and retry with the X-PAYMENT header. - ClientAvmSigner Implementation: Provides a complete Algorand signer class handling the raw-bytes-to-base64 encoding boundaries required by py-algorand-sdk. - Flexible Setup Options: Choose between convenience clients (x402HttpxClient, x402_requests), wrapping existing sessions, low-level transports/adapters, or config-based registration with specific networks and custom algod endpoints. - Use Case: You are building a Python service that consumes a paid API protected by x402 middleware on Algorand. Use this Skill to set up an httpx client that pays in USDC per request without writing payment logic yourself. ## Quick Start Ask the AI to create a Python x402 client using httpx that automatically pays for requests to a protected endpoint with my Algorand key from the AVM_PRIVATE_KEY environment variable.