ScorpTech x402 API

Ping

ping

Read-onlyIdempotent

Paid x402 test route for agents and client developers: the cheapest way to prove your x402 client signs a Solana USDC payment and the facilitator settles it before you call anything expensive. Returns pong, server time, your optional echo string and the payment terms; the settlement transaction comes back in the PAYMENT-RESPONSE header. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/ping

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ping"
  }
}

Input Schema

Name	Required	Description	Default
`echo`	No	Optional text echoed back (max 200 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotated readOnly/idempotent/openWorld hints, the description discloses that the call is billed ($0.001 USDC per successful call, Solana), that the pong/time/echo/payment-terms payload is returned, that the settlement transaction arrives in the PAYMENT-RESPONSE header, and that an HTTPS GET equivalent exists. That is exactly the context an annotations-only view would miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the 'cheapest way to verify' rationale are front-loaded, and every remaining clause (returns, price, header, HTTPS mirror) carries information an agent needs. Dense but justified; slightly long as a single run-on paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description enumerates the return values and explains where the settlement transaction appears, plus cost and transport details. Nothing material is missing for calling this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single optional 'echo' parameter, so the baseline is 3. The description adds semantic value by tying echo to the returned payload ('your optional echo string'), giving a reason to supply it, though it does not restate the 200-byte limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states exactly what the tool does: a paid x402 test route that proves a client can sign a Solana USDC payment and that the facilitator settles it. It also positions it against the rest of the catalog ('before you call anything expensive'), which lets an agent distinguish it from paid production endpoints and from the sibling x402_probe without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is explicit: use it as a cheap smoke test of x402 client signing/settlement before invoking expensive endpoints. It does not explicitly name the sibling x402_probe as the alternative or state when not to use it, so it falls short of a full when/when-not/alternative treatment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?