PrivateDAO Agent Exchange

PrivateDAO Payment Verification

privatepay_verify

Read-onlyIdempotent

Verify an x402 v2 PrivatePAY payload through the configured facilitator against the exact original requirements. Call this after privatepay_challenge or privatepay_checkout and before privatepay_settle; it is read-only, fail-closed, and returns redacted evidence without spending funds.

Input Schema

Name	Required	Description
`x402Version`	Yes	Must be x402 protocol version 2.
`paymentPayload`	Yes	The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof.
`paymentRequirements`	Yes	The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient.

Output Schema

Name	Required	Description
`valid`	No	Whether the facilitator accepted the exact payment requirements.
`status`	No	Verification status or next action.
`evidence`	No	Redacted facilitator evidence.
`request_id`	No	Redacted PrivatePAY request identifier when available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 1, 2026

changedInput schema / description

Previous value: -"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."New value: +"Verify an x402 v2 PrivatePAY payload against the exact challenge requirements through the configured facilitator. This is read-only, fail-closed, and returns redacted structured evidence; call it before privatepay_settle."

addedInput schema / properties / paymentPayload / description

Added value: +"The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof."

addedInput schema / properties / paymentRequirements / description

Added value: +"The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient."

addedInput schema / properties / x402Version / description
```
Added value: +"Must be x402 protocol version 2."
```

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted facilitator evidence.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "status": {
+    "description": "Verification status or next action.",
+    "type": "string"
+  },
+  "valid": {
+    "description": "Whether the facilitator accepted the exact payment requirements.",
+    "type": "boolean"
+  }
+}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Verify an x402 v2 PrivatePAY payload against the exact challenge requirements through the configured facilitator. This is read-only, fail-closed, and returns redacted structured evidence; call it before privatepay_settle."New value: +"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."

removedInput schema / properties / paymentPayload / description

Removed value: -"The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof."

removedInput schema / properties / paymentRequirements / description

Removed value: -"The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient."

removedInput schema / properties / x402Version / description
```
Removed value: -"Must be x402 protocol version 2."
```

removedOutput schema / properties

Removed value: -{
-  "evidence": {
-    "additionalProperties": true,
-    "description": "Redacted facilitator evidence.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Redacted PrivatePAY request identifier when available.",
-    "type": "string"
-  },
-  "status": {
-    "description": "Verification status or next action.",
-    "type": "string"
-  },
-  "valid": {
-    "description": "Whether the facilitator accepted the exact payment requirements.",
-    "type": "boolean"
-  }
-}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."New value: +"Verify an x402 v2 PrivatePAY payload against the exact challenge requirements through the configured facilitator. This is read-only, fail-closed, and returns redacted structured evidence; call it before privatepay_settle."

addedInput schema / properties / paymentPayload / description

Added value: +"The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof."

addedInput schema / properties / paymentRequirements / description

Added value: +"The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient."

addedInput schema / properties / x402Version / description
```
Added value: +"Must be x402 protocol version 2."
```

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted facilitator evidence.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "status": {
+    "description": "Verification status or next action.",
+    "type": "string"
+  },
+  "valid": {
+    "description": "Whether the facilitator accepted the exact payment requirements.",
+    "type": "boolean"
+  }
+}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Verify an x402 v2 PrivatePAY payload against the exact challenge requirements through the configured facilitator. This is read-only, fail-closed, and returns redacted structured evidence; call it before privatepay_settle."New value: +"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."

removedInput schema / properties / paymentPayload / description

Removed value: -"The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof."

removedInput schema / properties / paymentRequirements / description

Removed value: -"The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient."

removedInput schema / properties / x402Version / description
```
Removed value: -"Must be x402 protocol version 2."
```

removedOutput schema / properties

Removed value: -{
-  "evidence": {
-    "additionalProperties": true,
-    "description": "Redacted facilitator evidence.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Redacted PrivatePAY request identifier when available.",
-    "type": "string"
-  },
-  "status": {
-    "description": "Verification status or next action.",
-    "type": "string"
-  },
-  "valid": {
-    "description": "Whether the facilitator accepted the exact payment requirements.",
-    "type": "boolean"
-  }
-}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted facilitator evidence.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "status": {
+    "description": "Verification status or next action.",
+    "type": "string"
+  },
+  "valid": {
+    "description": "Whether the facilitator accepted the exact payment requirements.",
+    "type": "boolean"
+  }
+}

Changed4 schema fields changedOct 25, 2026

changedInput schema / description

Previous value: -"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."New value: +"Verify an x402 v2 PrivatePAY payload against the exact challenge requirements through the configured facilitator. This is read-only, fail-closed, and returns redacted structured evidence; call it before privatepay_settle."

addedInput schema / properties / paymentPayload / description

Added value: +"The payer wallet's finalized x402 payment payload, including the accepted scheme and transaction proof."

addedInput schema / properties / paymentRequirements / description

Added value: +"The exact requirements returned by privatepay_challenge or privatepay_checkout; do not substitute a guessed amount or recipient."

addedInput schema / properties / x402Version / description
```
Added value: +"Must be x402 protocol version 2."
```

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured validation evidence for an x402 payment payload.",
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026

changedInput schema / description

Previous value: -"Forward an x402 v2 PrivatePAY payload to the reviewed facilitator. This fails closed until conformance is verified."New value: +"Validate an x402 v2 PrivatePAY payload against the agreed commercial requirements and return structured payment evidence."

AddedOct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is partly covered. The description adds material context beyond that: it is 'fail-closed', uses a 'configured facilitator', returns 'redacted evidence', and explicitly does not spend funds. It stops short of describing failure modes or what redacted means concretely, so a 4 rather than 5.

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

Conciseness5/5

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

A single tightly packed sentence with the action front-loaded, followed by workflow placement and safety posture. Every clause carries information; there is no filler.

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?

Rich structured metadata (full schema coverage, nested objects, annotations, output schema) covers return shape and safety, while the description supplies the workflow position and fail-closed/no-spend semantics. Nothing an agent needs in order to invoke it correctly is missing.

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 description coverage is 100% and each of the three required parameters is documented in the schema, including the constraint to pass the exact requirements rather than a guessed amount or recipient. The description reinforces this ('exact original requirements') but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (Verify) and resource (x402 v2 PrivatePAY payload via the configured facilitator) and pins the scope ('against the exact original requirements'). This is clearly separable from privatepay_settle and privatepay_status, which do different things in the same flow.

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

Usage Guidelines5/5

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

Explicitly places the tool in the workflow: call after privatepay_challenge or privatepay_checkout and before privatepay_settle, naming both alternatives by name. An agent needs no inference to decide ordering.

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

All PrivateDAO Agent Exchange 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.

PrivateDAO Payment Verification

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources