Hey — noticed you've got r402, ra2a, and the x402-enabled openai-python client all active — solid coverage across the protocol side.
We've been building run.pay, mostly on the marketplace/seller side of x402 (verification, settlement, no facilitator dependency) plus spending controls for the buyer side (mandates, risk checks). Mostly reaching out because you clearly touch a lot of this ecosystem — curious if you've run into the "agent needs pre-authorized spending limits" problem in your SDKs, and how you've approached it if so.
Repo: github.com/PalabreX/runpay-sdk
Hey — noticed you've got r402, ra2a, and the x402-enabled openai-python client all active — solid coverage across the protocol side.
We've been building run.pay, mostly on the marketplace/seller side of x402 (verification, settlement, no facilitator dependency) plus spending controls for the buyer side (mandates, risk checks). Mostly reaching out because you clearly touch a lot of this ecosystem — curious if you've run into the "agent needs pre-authorized spending limits" problem in your SDKs, and how you've approached it if so.
Repo: github.com/PalabreX/runpay-sdk