111–116 of 116 posts
(a) Transaction fees. Network fees make microtransactions prohibitively expensive. This is the real problem.
(b) 3DS & latency issues If (a) is still the same, then meaningful transactions (eg.new accounts) would require human validation of sorts, which tenders the MPP use case very small.
Earlier quoted context omitted.
How do you keep customer information, credentials, and access secure from your employees (including yourself)?
If there are some admins, there will be always some people who will have access if shit hits the fan?
Earlier quoted context omitted.
This one is even worse IMO > Servers MAY return 402 when: > * Offering optional paid features or premium content This implies that a successful GET request to a resource that user already does have access to, might still return 402 instead of 200. This makes 402 basically unworkable.
An RFC is a request for comments, contributions. Are you open to contributing to this RFC?
How people here are handling this. When your agent hits a $35 API call, or gets stuck in a retry loop on a $0.50/req service, what stops it from draining the wallet?
Are wallet-level caps enough? Are you writing custom budget checks in your agent code? Or just not worrying about it yet?
We built an open source MCP proxy (github.com/policylayer/intercept) that enforces policy on tool calls. Thinking about extending it to read the -32042 payment challenge, check the amount against a budget, and allow/deny/hold for approval before the wallet pays.
Would love to hear if this is a real pain or a theoretical one.