Blockchain IQ x402 (remote, keyless)

The two tools have clearly disjoint purposes: list_endpoints is a read-only catalogue listing, while call_endpoint is the invocation path for a single resource. Descriptions reinforce the boundary and explicitly link them (use the id from the listing with call_endpoint).

Both names follow the same snake_case verb_noun pattern with the same object concept (endpoint/endpoints), differing only in singular versus plural, which is expected for list versus single-invoke semantics.

Two tools is minimal, but it fits a generic x402 catalogue gateway where the actual resources are data rather than tools, so adding more tools would be wrong. It is thin enough that the surface feels slightly narrow, but each tool clearly earns its place.

The server can discover and invoke free resources, but it holds no wallet, so paid resources cannot be completed without an out-of-band x402 client returning with a signed payload. That is a designed limitation, yet it leaves the paid half of the domain without an end-to-end in-server path and offers no payment-status or balance check.