x402 Agent Utilities

Each tool targets a clearly different object: on-chain token facts, webpage-to-Markdown conversion, and pre-payment inspection of an x402 endpoint. The shared mention of x402 pricing in every description is a billing detail, not a functional overlap, so an agent can pick the right tool unambiguously.

All three names use snake_case with a noun/modifier-then-action shape (token_check, web_to_markdown, x402_precheck). The x402_precheck name embeds a protocol token as prefix rather than a plain noun, which is a minor deviation but still readable and predictable.

Three tools is at the low end but each is a self-contained, non-redundant utility endpoint, so nothing feels padded. A small grab-bag utility server does not need a large surface, though one or two more endpoints would make it feel less sparse.

Coverage is notable-gapped for an 'x402 Agent Utilities' server: there is a precheck that never pays, but no tool to actually invoke/pay an x402 endpoint, and no generic HTTP or JSON transform utility. The three existing tools are coherent within themselves, but the surface leaves an agent unable to complete the pay-and-call lifecycle the name implies.