Machine Payments Protocol (MPP)
61–70 of 116 posts
Re: Machine Payments Protocol (MPP)
#62Earlier 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?
Re: Machine Payments Protocol (MPP)
#63Jokes about wallet-draining aside, we're already giving our agents a real cash budget that they use for tokens. Our harnesses have mechanisms to manage that spend. And having an easily detectable protocol would allow the harness to ensure that its deterministic code is in play to make these payments - you'd give your payment details to the harness, not to the agent itself. And as to use cases, if I want quality outpu…
> we're already giving our agents a real cash budget that they use for tokens. I read this line and my (poor little) brain ran in a whole other direction for a moment. Because AI token management and "parental controls" aren't that far separated functionally. How far are we from the AI companies selling token packs like video games sell premium currency? Buy NOW, 1.99 for 10,000 Anthropic gold...
And the gacha gaming industry knows exactly how to monetize this kind of trained instinct in a userbase. One might even call it a sense of pride and accomplishment...
(But, to my larger point, if agentic harnesses can offer their LLMs a source of reputable input tokens from professional content providers, as an alternative to just more token back-and-forth with the model provider... that harness can at least direct some of that money towards producers of well-researched content.)
Re: Machine Payments Protocol (MPP)
#64Regulation E limits your losses for electronic banking. Is this new payment system covered by Regulation E? What is the maximum loss a consumer would experience?
Re: Machine Payments Protocol (MPP)
#65I feel like the word "protocol", is just abused like it is a glorified marketing term. Kind of like how the word "hacker" was abused in everything else that had nothing to do with hacking. MCP was just a glorified way of tool calling but generated so much hype (and it eventually died down). Now we have MPP. Which again - could have just been another tool call exposed to the agent. Imagine you hire someone who claimed…
The good ol' folks at Stripe's collaborators Tempo Labs tried to make an RFC-style description page for MPP: https://paymentauth.org/ (full doc on IETF draft page: https://datatracker.ietf.org/doc/draft-ryan-httpauth-payment... ) I almost was going to point it out as evidence there was thought put into it. Nope, it's flimsy and AI generated. Also, it contains provisions for scamming customers: > 403 indicates the pay…
Re: Machine Payments Protocol (MPP)
#66I feel like the word "protocol", is just abused like it is a glorified marketing term. Kind of like how the word "hacker" was abused in everything else that had nothing to do with hacking. MCP was just a glorified way of tool calling but generated so much hype (and it eventually died down). Now we have MPP. Which again - could have just been another tool call exposed to the agent. Imagine you hire someone who claimed…
The good ol' folks at Stripe's collaborators Tempo Labs tried to make an RFC-style description page for MPP: https://paymentauth.org/ (full doc on IETF draft page: https://datatracker.ietf.org/doc/draft-ryan-httpauth-payment... ) I almost was going to point it out as evidence there was thought put into it. Nope, it's flimsy and AI generated. Also, it contains provisions for scamming customers: > 403 indicates the pay…
On topic though, Stripe is trying to make themselves the Visa/Mastercard of crypto. They're in position to do so and it seems like Coinbase is their other half. I don't trust or like it though.