x402 V2 discovery manifest.

F3: the stock x402 client does discovery via the 402 challenge itself (request -> 402 + PAYMENT-REQUIRED header -> decode -> pay -> retry); the library has no manifest endpoint of its own. This manifest is a project-level convenience so agents can pre-fetch machine-readable pricing for every endpoint without first paying a 402 round-trip.

Structure: uses a resources array (x402 V2 spec standard) where each entry has its own accepts[] (payment requirements) flattened at the resource level.

Each resource includes:

• url — absolute URL for crawler/agent resolution
• method + path — standard HTTP routing
• description — what the endpoint returns
• price / amount — human-readable and raw USDC cost
• requiredQueryParams — query params agents must supply (list)
• accepts[] — payment requirements (camelCase, same as the 402 challenge)