PrivateDAO Agent Exchange

PrivateDAO Payment Challenge

privatepay_challenge

Idempotent

Create a fresh PrivatePAY x402 v2 challenge for a resource and quoted USDC amount. Call this before privatepay_verify; it returns exact payment requirements and the PDAO private-settlement rule, but never signs, broadcasts, or charges a wallet.

Input Schema

Name	Required	Description
`nonce`	No	Optional caller nonce used to bind a fresh challenge.
`resource`	Yes	Stable HTTPS resource or service identifier being purchased.
`mime_type`	No	Optional response media type for the purchased resource.
`provider_id`	Yes	PrivatePAY provider or merchant identifier.
`amount_base_units`	Yes	Quoted USDC amount in token base units, not a decimal display amount.

Output Schema

Name	Required	Description
`privacy`	No	Redacted privacy boundary for the challenge.
`request_id`	No	Fresh challenge or payment request identifier.
`payment_required`	No	Exact x402 v2 requirements to present to the payer.
`payment_required_header`	No	HTTP PAYMENT-REQUIRED value when returned by the checkout flow.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 1, 2026

changedInput schema / description

Previous value: -"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."New value: +"Create a fresh PrivatePAY x402 v2 challenge after checking rail status. This returns payment requirements and the PDAO private-settlement rule; it does not sign, broadcast, or move funds."

addedInput schema / properties / amount_base_units / description

Added value: +"Quoted USDC amount in token base units, not a decimal display amount."

addedInput schema / properties / mime_type / description

Added value: +"Optional response media type for the purchased resource."

addedInput schema / properties / nonce / description

Added value: +"Optional caller nonce used to bind a fresh challenge."

addedInput schema / properties / provider_id / description

Added value: +"PrivatePAY provider or merchant identifier."

addedInput schema / properties / resource / description

Added value: +"Stable HTTPS resource or service identifier being purchased."

addedOutput schema / properties

Added value: +{
+  "payment_required": {
+    "additionalProperties": true,
+    "description": "Exact x402 v2 requirements to present to the payer.",
+    "type": "object"
+  },
+  "payment_required_header": {
+    "description": "HTTP PAYMENT-REQUIRED value when returned by the checkout flow.",
+    "type": "string"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Redacted privacy boundary for the challenge.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Fresh challenge or payment request identifier.",
+    "type": "string"
+  }
+}

Changed7 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Create a fresh PrivatePAY x402 v2 challenge after checking rail status. This returns payment requirements and the PDAO private-settlement rule; it does not sign, broadcast, or move funds."New value: +"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."

removedInput schema / properties / amount_base_units / description

Removed value: -"Quoted USDC amount in token base units, not a decimal display amount."

removedInput schema / properties / mime_type / description

Removed value: -"Optional response media type for the purchased resource."

removedInput schema / properties / nonce / description

Removed value: -"Optional caller nonce used to bind a fresh challenge."

removedInput schema / properties / provider_id / description

Removed value: -"PrivatePAY provider or merchant identifier."

removedInput schema / properties / resource / description

Removed value: -"Stable HTTPS resource or service identifier being purchased."

removedOutput schema / properties

Removed value: -{
-  "payment_required": {
-    "additionalProperties": true,
-    "description": "Exact x402 v2 requirements to present to the payer.",
-    "type": "object"
-  },
-  "payment_required_header": {
-    "description": "HTTP PAYMENT-REQUIRED value when returned by the checkout flow.",
-    "type": "string"
-  },
-  "privacy": {
-    "additionalProperties": true,
-    "description": "Redacted privacy boundary for the challenge.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Fresh challenge or payment request identifier.",
-    "type": "string"
-  }
-}

Changed7 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."New value: +"Create a fresh PrivatePAY x402 v2 challenge after checking rail status. This returns payment requirements and the PDAO private-settlement rule; it does not sign, broadcast, or move funds."

addedInput schema / properties / amount_base_units / description

Added value: +"Quoted USDC amount in token base units, not a decimal display amount."

addedInput schema / properties / mime_type / description

Added value: +"Optional response media type for the purchased resource."

addedInput schema / properties / nonce / description

Added value: +"Optional caller nonce used to bind a fresh challenge."

addedInput schema / properties / provider_id / description

Added value: +"PrivatePAY provider or merchant identifier."

addedInput schema / properties / resource / description

Added value: +"Stable HTTPS resource or service identifier being purchased."

addedOutput schema / properties

Added value: +{
+  "payment_required": {
+    "additionalProperties": true,
+    "description": "Exact x402 v2 requirements to present to the payer.",
+    "type": "object"
+  },
+  "payment_required_header": {
+    "description": "HTTP PAYMENT-REQUIRED value when returned by the checkout flow.",
+    "type": "string"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Redacted privacy boundary for the challenge.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Fresh challenge or payment request identifier.",
+    "type": "string"
+  }
+}

Changed7 schema fields changedOct 28, 2026

changedInput schema / description

Previous value: -"Create a fresh PrivatePAY x402 v2 challenge after checking rail status. This returns payment requirements and the PDAO private-settlement rule; it does not sign, broadcast, or move funds."New value: +"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."

removedInput schema / properties / amount_base_units / description

Removed value: -"Quoted USDC amount in token base units, not a decimal display amount."

removedInput schema / properties / mime_type / description

Removed value: -"Optional response media type for the purchased resource."

removedInput schema / properties / nonce / description

Removed value: -"Optional caller nonce used to bind a fresh challenge."

removedInput schema / properties / provider_id / description

Removed value: -"PrivatePAY provider or merchant identifier."

removedInput schema / properties / resource / description

Removed value: -"Stable HTTPS resource or service identifier being purchased."

removedOutput schema / properties

Removed value: -{
-  "payment_required": {
-    "additionalProperties": true,
-    "description": "Exact x402 v2 requirements to present to the payer.",
-    "type": "object"
-  },
-  "payment_required_header": {
-    "description": "HTTP PAYMENT-REQUIRED value when returned by the checkout flow.",
-    "type": "string"
-  },
-  "privacy": {
-    "additionalProperties": true,
-    "description": "Redacted privacy boundary for the challenge.",
-    "type": "object"
-  },
-  "request_id": {
-    "description": "Fresh challenge or payment request identifier.",
-    "type": "string"
-  }
-}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties

Added value: +{
+  "payment_required": {
+    "additionalProperties": true,
+    "description": "Exact x402 v2 requirements to present to the payer.",
+    "type": "object"
+  },
+  "payment_required_header": {
+    "description": "HTTP PAYMENT-REQUIRED value when returned by the checkout flow.",
+    "type": "string"
+  },
+  "privacy": {
+    "additionalProperties": true,
+    "description": "Redacted privacy boundary for the challenge.",
+    "type": "object"
+  },
+  "request_id": {
+    "description": "Fresh challenge or payment request identifier.",
+    "type": "string"
+  }
+}

Changed6 schema fields changedOct 25, 2026

changedInput schema / description

Previous value: -"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."New value: +"Create a fresh PrivatePAY x402 v2 challenge after checking rail status. This returns payment requirements and the PDAO private-settlement rule; it does not sign, broadcast, or move funds."

addedInput schema / properties / amount_base_units / description

Added value: +"Quoted USDC amount in token base units, not a decimal display amount."

addedInput schema / properties / mime_type / description

Added value: +"Optional response media type for the purchased resource."

addedInput schema / properties / nonce / description

Added value: +"Optional caller nonce used to bind a fresh challenge."

addedInput schema / properties / provider_id / description

Added value: +"PrivatePAY provider or merchant identifier."

addedInput schema / properties / resource / description

Added value: +"Stable HTTPS resource or service identifier being purchased."

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured PrivatePAY x402 challenge and payment requirements.",
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026

changedInput schema / description

Previous value: -"Request a PrivatePAY x402 V2 PaymentRequired object. This is unavailable until a reviewed confidential privacy rail is configured."New value: +"Create a structured PrivatePAY x402 V2 payment challenge for an eligible commercial workflow."

AddedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds genuine context beyond the annotations: it 'never signs, broadcasts, or charges a wallet,' which resolves the tension of readOnlyHint=false and confirms non-destructive behavior, and it discloses the return payload (payment requirements plus PDAO private-settlement rule). It does not explain challenge lifetime/expiry or how idempotentHint=true interacts with the 'fresh challenge' language and the optional nonce.

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 dense sentences, front-loaded with the action and followed by the ordering constraint and safety guarantee. No filler or restatement of the tool name.

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?

Annotations plus an output schema carry most of the load, and the description covers preconditions and side-effect profile well. It leaves ambiguous how this challenge relates to privatepay_prepare/settle/checkout in the broader payment flow, which matters given the crowded privatepay_* family.

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%, so all five parameters are already documented in the schema, including the base-units caveat. The description only restates resource and amount at a high level and adds no semantics for provider_id, mime_type, or nonce binding, so the baseline 3 applies.

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?

Specific verb+resource: 'Create a fresh PrivatePAY x402 v2 challenge' with the inputs (resource, quoted USDC amount) named. It distinguishes itself from privatepay_verify by stating ordering, but not from other siblings such as privatepay_prepare, privatepay_checkout, or privatepay_settle.

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?

Explicit sequencing: 'Call this before privatepay_verify.' The pre-condition is also reinforced in the schema description ('after checking rail status'). No when-not guidance or alternative routing against the other privatepay_* tools, so it stops short of a 5.

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 Challenge

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources