Official Source Evidence

The four get_*_ayment tools all create live x402 challenges and differ only by product, while get_quote and get_example_payment both provide example input data — creating real selection ambiguity. Descriptions do clarify the product and side-effect differences, but an agent must read carefully to avoid picking the wrong one.

All tools use lowercase snake_case with a verb prefix, and the get_X_payment pattern for challenge creation is consistent. However, 'get' is overloaded to cover both free reads that create no side effects and challenge creation calls, and get_payment_preflight_payment has a redundant 'ayment' that muddies the naming pattern.

Eight tools map cleanly to the paid-evidence workflow: status check, quote, four product-specific challenge creators, payment submission, and a capability-request escape hatch. Each tool earns its place, and the count is well-scoped for a niche paid API.

The core quote→challenge→submit→result flow is covered, and request_capability is a good gap-filler for missing products. Minor gaps remain: there is no explicit result-retrieval tool beyond request_id replay, and product discovery is implicit through get_quote and get_service_status rather than a dedicated list endpoint.