PrivateDAO Agent Exchange

PrivateDAO Payment Settlement

privatepay_settle

Destructive

Settle an already verified x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call this only after privatepay_verify with unchanged requirements; this is the payment-moving action and may create facilitator-side or on-chain settlement.

Input Schema

Name	Required	Description
`x402Version`	Yes	Must be x402 protocol version 2.
`paymentPayload`	Yes	The same finalized payer payload that passed privatepay_verify.
`paymentRequirements`	Yes	The unchanged requirements from the original PrivatePAY challenge.

Output Schema

Name	Required	Description
`status`	No	Settlement status.
`settled`	No	Whether the facilitator accepted settlement.
`evidence`	No	Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.
`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: -"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."New value: +"Settle an already authorized x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call privatepay_verify first; this is the only payment-moving PrivatePAY tool and may create a facilitator or on-chain settlement."

addedInput schema / properties / paymentPayload / description

Added value: +"The same finalized payer payload that passed privatepay_verify."

addedInput schema / properties / paymentRequirements / description

Added value: +"The unchanged requirements from the original PrivatePAY challenge."

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

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "settled": {
+    "description": "Whether the facilitator accepted settlement.",
+    "type": "boolean"
+  },
+  "status": {
+    "description": "Settlement status.",
+    "type": "string"
+  }
+}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Settle an already authorized x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call privatepay_verify first; this is the only payment-moving PrivatePAY tool and may create a facilitator or on-chain settlement."New value: +"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."

removedInput schema / properties / paymentPayload / description

Removed value: -"The same finalized payer payload that passed privatepay_verify."

removedInput schema / properties / paymentRequirements / description

Removed value: -"The unchanged requirements from the original PrivatePAY challenge."

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

removedOutput schema / properties

Removed value: -{
-  "evidence": {
-    "additionalProperties": true,
-    "description": "Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Redacted PrivatePAY request identifier when available.",
-    "type": "string"
-  },
-  "settled": {
-    "description": "Whether the facilitator accepted settlement.",
-    "type": "boolean"
-  },
-  "status": {
-    "description": "Settlement status.",
-    "type": "string"
-  }
-}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."New value: +"Settle an already authorized x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call privatepay_verify first; this is the only payment-moving PrivatePAY tool and may create a facilitator or on-chain settlement."

addedInput schema / properties / paymentPayload / description

Added value: +"The same finalized payer payload that passed privatepay_verify."

addedInput schema / properties / paymentRequirements / description

Added value: +"The unchanged requirements from the original PrivatePAY challenge."

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

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "settled": {
+    "description": "Whether the facilitator accepted settlement.",
+    "type": "boolean"
+  },
+  "status": {
+    "description": "Settlement status.",
+    "type": "string"
+  }
+}

Changed5 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Settle an already authorized x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call privatepay_verify first; this is the only payment-moving PrivatePAY tool and may create a facilitator or on-chain settlement."New value: +"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."

removedInput schema / properties / paymentPayload / description

Removed value: -"The same finalized payer payload that passed privatepay_verify."

removedInput schema / properties / paymentRequirements / description

Removed value: -"The unchanged requirements from the original PrivatePAY challenge."

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

removedOutput schema / properties

Removed value: -{
-  "evidence": {
-    "additionalProperties": true,
-    "description": "Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Redacted PrivatePAY request identifier when available.",
-    "type": "string"
-  },
-  "settled": {
-    "description": "Whether the facilitator accepted settlement.",
-    "type": "boolean"
-  },
-  "status": {
-    "description": "Settlement status.",
-    "type": "string"
-  }
-}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties

Added value: +{
+  "evidence": {
+    "additionalProperties": true,
+    "description": "Redacted settlement evidence; provider secrets and sensitive payment payloads are excluded.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Redacted PrivatePAY request identifier when available.",
+    "type": "string"
+  },
+  "settled": {
+    "description": "Whether the facilitator accepted settlement.",
+    "type": "boolean"
+  },
+  "status": {
+    "description": "Settlement status.",
+    "type": "string"
+  }
+}

Changed4 schema fields changedOct 25, 2026

changedInput schema / description

Previous value: -"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."New value: +"Settle an already authorized x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call privatepay_verify first; this is the only payment-moving PrivatePAY tool and may create a facilitator or on-chain settlement."

addedInput schema / properties / paymentPayload / description

Added value: +"The same finalized payer payload that passed privatepay_verify."

addedInput schema / properties / paymentRequirements / description

Added value: +"The unchanged requirements from the original PrivatePAY challenge."

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 PrivatePAY settlement evidence.",
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026

changedInput schema / description

Previous value: -"Request x402 v2 PrivatePAY settlement through the reviewed facilitator. This may move funds only after explicit production activation."New value: +"Request x402 v2 PrivatePAY settlement through the configured payment workflow and return structured settlement evidence."

AddedOct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the description's job is to add context, which it does by disclosing that it moves payment and may create facilitator-side or on-chain settlement, plus that output is redacted. It stops short of warning about duplicate settlement on retry (relevant since idempotentHint=false with real money) or permission/config prerequisites for the facilitator.

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?

Two sentences, no filler, with the prerequisite and the destructive side effect front-loaded before any agent commits to the call. Every clause carries decision-relevant information.

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

Completeness4/5

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

Output schema exists, so return-value detail is unnecessary, and annotations carry the safety profile. The description supplies the precondition and mutation scope, leaving only retry/idempotency guidance and failure-mode behavior as gaps for a money-moving operation.

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 100% and the schema's own property descriptions already say the payload must be 'the same finalized payer payload that passed privatepay_verify' and requirements must be 'unchanged.' The description's 'unchanged requirements' phrasing echoes that, adding little beyond the structured fields; 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 (Settle), a specific resource (an already verified x402 v2 PrivatePAY payload), the execution channel (configured facilitator), and the return (redacted settlement evidence). This distinguishes it cleanly from privatepay_verify and other siblings without needing to open the schema.

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 gated: 'Call this only after privatepay_verify with unchanged requirements', naming the prerequisite sibling tool and the condition that selects it. It also flags this as the payment-moving action, which tells an agent when this tool is the right choice versus the read-only verification steps.

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 Settlement

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources