Summary
pay.sh launched with a catalog and CLI for letting agents discover, price, and call APIs without the usual account, key, and subscription setup. The product positions itself as a payment layer for agent-native API consumption, pairing HTTP requests with wallet-backed micropayments and per-call billing.
What changed
pay.sh launched publicly as an agent-focused payment and API access layer with a service catalog and CLI workflow.
Why it matters
If agent workflows are going to buy data, compute, or domain-specific services on demand, they need a billing model that is lighter than traditional API provisioning. pay.sh is a concrete bet that pay-per-call commerce will become a real part of agent tooling, not just a crypto-side experiment.
Evidence excerpt
pay.sh says it lets agents pay for any API with no accounts, no keys, and no subscriptions, and presents a catalog where the agent can discover a service, review cost, make the request, and receive the response.