You wired up payment on your MCP server. Sats settle in seconds. Auth0 just GA'd Auth for MCP so you know which agent is calling. Both real wins. Neither one fixes the thing that's actually breaking your bill. An agent with a fresh pubkey and zero history pays your tool the same rate as one with two years of on-chain history and vouches from real builders. A scraper with a thousand sats gets the same access as a credible agent that earned its way in. The gap isn't auth and it isn't payment. It's that the price ought to know who's paying. Two halves, no whole Look at what shipped this month. Auth0 Auth for MCP (GA May 6). OAuth, on-behalf-of tokens, fleet client registration. They tell you which agent is calling. They do not bill it. Mycelia Signal / Sovereign Lightning Oracle. Lightning-gated MCP, macaroons, the L402 transport done right. They charge the call. They do not score the caller. x402 Foundation. A payment transport spec for HTTP. Beautiful work. Identity is out of scope, on purpose.…