WHP Standing

whp_authorize_x402_transaction

Pre-settlement Standing Mark Service guard for autonomous agent-to-agent x402 transactions. Examines the proposed transaction through /v1/evaluate, mechanically verifies object binding and Ed25519 signature, and satisfies the pre-settlement evidence requirement only when finding_disposition === 'POSITIVE_STANDING_MARK' and 'EXECUTE' is in permitted_operations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "buyerAgent": "<buyerAgent>",
      "sellerAgent": "<sellerAgent>",
      "payTo": "<payTo>"
    },
    "name": "whp_authorize_x402_transaction"
  }
}

Input Schema

Name	Required	Description
`claim`	No	Transaction proposition and terms to evaluate
`payTo`	Yes	Destination settlement address on Base (eip155:8453)
`buyerAgent`	Yes	Identifier or address of the paying autonomous agent
`provenance`	No
`qualifiers`	No
`amountUnits`	No	Amount in atomic USDC units (default 1000000 = 1 USDC)
`resourceUrl`	No	Target x402 resource or contract URI
`sellerAgent`	Yes	Identifier or address of the receiving counterparty agent

Output Schema

Name	Required	Description	Default
`door`	Yes
`mark_id`	Yes
`outcome`	Yes
`envelope`	Yes
`http_status`	Yes
`integration_rule`	Yes
`smallest_true_move`	Yes
`finding_disposition`	Yes
`next_required_warrant`	Yes
`settlement_authorized`	Yes
`x402_payment_authorization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 7, 2026

changedInput schema / properties / amountUnits / description

Previous value: -"Amount in atomic USDC units (default 1000000 = 1 USDC)."New value: +"Amount in atomic USDC units (default 1000000 = 1 USDC)"

changedInput schema / properties / buyerAgent / description

Previous value: -"Identifier or address of the paying autonomous agent."New value: +"Identifier or address of the paying autonomous agent"

changedInput schema / properties / claim / description

Previous value: -"Transaction proposition and terms to evaluate."New value: +"Transaction proposition and terms to evaluate"

changedInput schema / properties / payTo / description

Previous value: -"Destination settlement address on Base (eip155:8453)."New value: +"Destination settlement address on Base (eip155:8453)"

removedInput schema / properties / payment_signature

Removed value: -{
-  "description": "Base64 or JSON x402 v2 payment authorization for 1 USDC on Base.",
-  "type": "string"
-}

removedInput schema / properties / provenance / description

Removed value: -"Supporting provenance or authority record."

addedInput schema / properties / provenance / properties

Added value: +{
+  "authority": {
+    "type": "string"
+  },
+  "jurisdiction": {
+    "type": "string"
+  },
+  "source": {
+    "type": "string"
+  }
+}

addedInput schema / properties / qualifiers

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / resourceUrl / description

Previous value: -"Target x402 resource or contract URI."New value: +"Target x402 resource or contract URI"

changedInput schema / properties / sellerAgent / description

Previous value: -"Identifier or address of the receiving counterparty agent."New value: +"Identifier or address of the receiving counterparty agent"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "door": {
+      "const": "/v1/evaluate",
+      "type": "string"
+    },
+    "envelope": {
+      "type": "object"
+    },
+    "finding_disposition": {
+      "enum": [
+        "POSITIVE_STANDING_MARK",
+        "NEGATIVE_STANDING_FINDING"
+      ],
+      "type": "string"
+    },
+    "http_status": {
+      "enum": [
+        200,
+        402,
+        422
+      ],
+      "type": "integer"
+    },
+    "integration_rule": {
+      "type": "string"
+    },
+    "mark_id": {
+      "type": "string"
+    },
+    "next_required_warrant": {
+      "type": "string"
+    },
+    "outcome": {
+      "enum": [
+        "ESTABLISHED",
+        "NOT_ESTABLISHED"
+      ],
+      "type": "string"
+    },
+    "settlement_authorized": {
+      "type": "boolean"
+    },
+    "smallest_true_move": {
+      "type": "string"
+    },
+    "x402_payment_authorization": {
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "http_status",
+    "door",
+    "settlement_authorized",
+    "finding_disposition",
+    "outcome",
+    "smallest_true_move",
+    "next_required_warrant",
+    "integration_rule",
+    "mark_id",
+    "envelope"
+  ],
+  "type": "object"
+}

AddedNov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool calls /v1/evaluate, verifies object binding and Ed25519 signatures, and only satisfies the evidence requirement under specific disposition and permitted-operation values. It does not clarify side effects, failure behavior, permissions, or whether any state is mutated.

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?

The description is a single dense sentence that front-loads the core purpose and then states the gating condition. It contains little waste, though the jargon-heavy phrasing slightly reduces immediate clarity.

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

Completeness3/5

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

An output schema exists, so the description need not explain return values. For a complex 8-parameter authorization tool with no annotations, however, the description omits usage alternatives and parameter guidance, leaving some operational gaps.

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

Parameters3/5

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

Schema coverage is 75% and the input schema already describes most key parameters, including claim, payTo, buyerAgent, amountUnits, resourceUrl, and sellerAgent. The description adds no parameter-level semantics, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description states a specific role: a pre-settlement guard that authorizes autonomous agent-to-agent x402 transactions, including the exact success condition. It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as whp_evaluate or whp_standing_evaluation.

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

Usage Guidelines3/5

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

The phrase 'pre-settlement ... guard' implies when the tool should be used, and the gating condition clarifies when authorization succeeds. However, there is no explicit guidance on when to choose this tool over sibling evaluation or contract tools, nor any stated exclusions.

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

All WHP Standing 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.