stripe / purl

The CLI itself installs via Homebrew (brew install stripe/purl/purl) or by building from source with Rust, and it is built around a wallet you set up once with purl wallet add. From there, purl <url> pays for and fetches a resource that responds with an x402 payment requirement, purl inspect shows what a resource would charge before you commit, purl --dry-run previews a payment without sending it, and purl balance reports what is left in the wallet. The one skill, pay-for-http-request, wires an agent into that same flow: it uses the purl CLI to make paid requests automatically instead of a person running the command by hand.

What that means before you install it. The README's own advice — "it is recommended to use a wallet dedicated for usage with purl" — is there because this skill can authorize real spending on an agent's behalf; --confirm requires a manual yes per request, but it is off by default. There is nothing in the material we have about spending limits or a way to cap what an agent can authorize beyond that flag.

READ THE FULL ANALYSIS＋

One skill, no wrapper content around it. The repository is the CLI and its documentation; there is no second skill, no page grouping, and nothing else here to describe beyond what purl itself does.