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 to have invented a new protocol and you're thinking of something like TCP or UDP, but all they share is just a markdown file.

And as to use cases, if I want quality outputs for automated research and discovery of a topic, in a world where quality journalism/scholarship should be compensated and does use tools like Cloudflare to block automated access, and where AI-generated content is everywhere, it's optimal for me to want to spend some amount of the money I spend on tokens, on the ability for my agent to access reputable primary and secondary sources as needed.

The challenge, of course, is that now there's an incentive for a spam source to try to get my agent to pay it, rather than the actual creator of the content. But there are interesting ways to solve this, because with these payment rails there's now an incentive for alliances of content creators to maintain indices of reputable sources and their canonical domains - perhaps even authoritative hashes of content. Lots of possibilities here.

Please let us know if you have suggestions of what complex workflows you would like to build.

Really, they _need_ it. How can we possibly live without computers spending money without supervision?

Is this an attempt to get multiple payment processors to adopt the same Payments API so that agents fail less often?

Note the absence of invoices, bills of lading, and receipts, all the things you need when a vendor doesn't deliver. All it does is send money, one-way. So it's useless in a B2B context.

A well thought out proposal for the long term, unlike MCP which is a complete joke of a "standard" and broken by design.

[0] https://paymentauth.org/

[1] https://datatracker.ietf.org/doc/draft-ryan-httpauth-payment...