In the conversation with @corbits_dev, we talked about the awkwardness of having the x402 middleware construct the initial 402 response. Which hardcodes rules and assumptions in SDK code that's hard to update and adds unwanted dependencies. We agreed that this logic should live in the facilitator, so I just exposed a /accepts endpoint in the thirdweb facilitator that does just that. You give it your minimal configuration and it returns a fully populated 402 response. Very handy for non-JS backends, and will also make it WAY easier to move to the upcoming v2 format. Shipped in v5.111.0 of the thirdweb SDK, and live in the facilitator API: