[dead]
Machine Payments Protocol (MPP)
91–100 of 116 posts
Re: Machine Payments Protocol (MPP)
#92I 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…
I mean, I have had people unironically declare they had written compilers or exploits, which were actually just javascript or golang wrappers around the real payload, or all of the irrelevant lexer/parser/typechecker/optimizer/assembler bits.. I'm sure they were just as trivial, especially today with LLMs..
Re: Machine Payments Protocol (MPP)
#93Earlier quoted context omitted.
> 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...
There was another comment I recall from today, discussing how OpenAI is not-so-subtly adopting a social-network-esque model, in how it's fine-tuned its chat system to always suggest another question that the user might want to ask. 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 po…
> how OpenAI is not-so-subtly adopting a social-network-esque model, in how it's fine-tuned its chat system to always suggest another question that the user might want to ask.
There’s that, but it could also be adaptation to the fact users… just don’t know what to do with it.
Just like the prompt suggestions they added for new conversations a little time after releasing the first app. Those seem to be mostly gone now, at least on mobile.
Re: Machine Payments Protocol (MPP)
#94x402 is more of a protocol than this
Re: Machine Payments Protocol (MPP)
#95You guys, when you use AI to solve some question or task and it succeeds, do you feel like typing "Thank You" to your LLM/Agent? I do feel that way often, but then I think that would be crazy, a waste of keystrokes an maybe also tokens, why would I do that? Yet I feel tempted to do that frequently.
But then I also wonder if this attitude "Why should I waste time thanking it?" will also spread to human-human interactions?
Re: Machine Payments Protocol (MPP)
#96You guys, when you use AI to solve some question or task and it succeeds, do you feel like typing "Thank You" to your LLM/Agent? I do feel that way often, but then I think that would be crazy, a waste of keystrokes an maybe also tokens, why would I do that? Yet I feel tempted to do that frequently. But then I also wonder if this attitude "Why should I waste time thanking it?" will also spread to human-human interacti…
"Sam Altman considers it a worthwhile expense":
https://www.tomshardware.com/tech-industry/artificial-intell...
Re: Machine Payments Protocol (MPP)
#97Earlier quoted context omitted.
And https://www.x402.org/
Yep x402 is for any blockchain rather than just Stripe. I use it: it’s like being able to access a service without having to sign up and get an API key.
How do you use it? I explored building on this as a platform but ditched it because only crypto nerds seem to use it and fiat is used all around anyway.
Re: Machine Payments Protocol (MPP)
#98Nobody pointing out that this offers zero advantage over traditional API?
Re: Machine Payments Protocol (MPP)
#99Nobody pointing out that this offers zero advantage over traditional API?
> As an alternative to setting up an account and getting an API key, your agent can interact with services on demand and pay per invocation. Your agents only needs access to a crypto wallet.
Let's say I wanted to ask an agent to use Google Maps APIs to produce a look-up of all bakeries in a city, say, and then find all their mentions across platforms - e.g. Twitter, Reddit, Yelp, etc etc.
Without something like this, I'd need to manually set up accounts across multiple platforms, all with different billing/subscription cycles. Go through account set-up/validation. Then give an agent an API key with potentially unrestricted access — it might run up a huge bill, or could get my account suspended if it goes a bit haywire and starts spamming calls, say.
If vendors decided to all support the protocol, I could give an agent $10, tell it the task and let it go without any of the manual handholding but with a hardcap on what it can spend if something goes wrong.
Re: Machine Payments Protocol (MPP)
#100You're absolutely right! I should have sent $5.00 for that transaction and not $500,000. I will generate a letter for you to print and sign and send to your bank to notify them of my mistake. Would you like me to generate a bankruptcy filing for you as well?
LLMs rarely admit fault, you gotta shift blame onto the user: > You're absolutely right! The transaction was submitted as $500,000 instead of $5.00. Since that's what was entered on your end, you'll need to contact your bank to resolve it. I will generate a letter for you to print, sign, and send to your bank if needed. Would you like me to generate a bankruptcy filing for you as well?
It's backed by a crypto wallet that it's using for its funds - if you decide to put $500k into the wallet that you've giving carte blanche access to an LLM, maybe you do deserve to shoulder some of the blame