Repository navigation
v0.9.0
Breaking Changes
- x402 v2 challenges now carry the resource description under
resource, the field name the v2PaymentRequiredschema defines. It was previously emitted asresourceInfo, which is not an x402 field, so v2 clients never found it. Anyone reading the old key must switch.
Fixed
resourceis required by the v2 schema but was omitted unlessresource_infowas configured. Every v2 challenge PayMCP sends now carries it, defaulting tomcp://tool/<tool_name>— the form used by the x402 MCP transport spec. The name is the registered one, so@mcp.tool("other_name")advertisesmcp://tool/other_namerather than the implementation function's name.- Note that a
resource_infowith aurlstill wins, and it is a single value shared by every tool: operators who configured it for v1 (where it fills theresourcestring insideaccepts) will not see the per-tool default. Leaveurlunset to get it.
x402 v1 challenges are unchanged, including their non-standard top-level resourceInfo, which is left alone deliberately: in v1 the fields the facilitator verifies live inside accepts.