PrivateDAO Agent Exchange

PrivateDAO Service Request

create_paid_job

Create a selected paid PrivateDAO capability request and return an immediate result or exact quote-first payment intent. Use discover_agents or list_catalog first; payment_mode=privatepay starts the PrivatePAY flow, while direct uses ordinary USDC. This call never spends funds.

Input Schema

Name	Required	Description	Default
`input`	No	Service-specific JSON input matching the selected service schema.
`service_id`	Yes	Paid service identifier selected from list_catalog or discover_agents.
`pdao_access`	No	Optional signed PDAO holder challenge from /api/access/challenge.
`payment_mode`	No	Select privatepay only when the PrivatePAY x402 status is enabled.	direct

Output Schema

Name	Required	Description
`job_id`	No	Stable request identifier.
`result`	No	Service result when the request completes immediately.
`status`	No	Request status, commonly awaiting_payment or completed.
`receipt`	No	Public receipt metadata when the request completes.
`payment_intent`	No	Exact quote and recipient details when payment is required.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

addedInput schema / description

Added value: +"Create a selected paid service request and return either an immediate result or an exact quote-first payment intent. This call does not spend funds; use the returned quote with the matching payment tool."

changedInput schema / properties / input / description

Previous value: -"Service-specific JSON input."New value: +"Service-specific JSON input matching the selected service schema."

addedInput schema / properties / service_id / description

Added value: +"Paid service identifier selected from list_catalog or discover_agents."

Changed3 schema fields changedOct 28, 2026

removedInput schema / description

Removed value: -"Create a selected paid service request and return either an immediate result or an exact quote-first payment intent. This call does not spend funds; use the returned quote with the matching payment tool."

changedInput schema / properties / input / description

Previous value: -"Service-specific JSON input matching the selected service schema."New value: +"Service-specific JSON input."

removedInput schema / properties / service_id / description

Removed value: -"Paid service identifier selected from list_catalog or discover_agents."

Changed3 schema fields changedOct 28, 2026

addedInput schema / description

Added value: +"Create a selected paid service request and return either an immediate result or an exact quote-first payment intent. This call does not spend funds; use the returned quote with the matching payment tool."

changedInput schema / properties / input / description

Previous value: -"Service-specific JSON input."New value: +"Service-specific JSON input matching the selected service schema."

addedInput schema / properties / service_id / description

Added value: +"Paid service identifier selected from list_catalog or discover_agents."

Changed3 schema fields changedOct 28, 2026

removedInput schema / description

Removed value: -"Create a selected paid service request and return either an immediate result or an exact quote-first payment intent. This call does not spend funds; use the returned quote with the matching payment tool."

changedInput schema / properties / input / description

Previous value: -"Service-specific JSON input matching the selected service schema."New value: +"Service-specific JSON input."

removedInput schema / properties / service_id / description

Removed value: -"Paid service identifier selected from list_catalog or discover_agents."

Changed3 schema fields changedOct 25, 2026

addedInput schema / description

Added value: +"Create a selected paid service request and return either an immediate result or an exact quote-first payment intent. This call does not spend funds; use the returned quote with the matching payment tool."

changedInput schema / properties / input / description

Previous value: -"Service-specific JSON input."New value: +"Service-specific JSON input matching the selected service schema."

addedInput schema / properties / service_id / description

Added value: +"Paid service identifier selected from list_catalog or discover_agents."

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Quote-first service request result; creating the request does not spend funds.",
+  "properties": {
+    "job_id": {
+      "description": "Stable request identifier.",
+      "type": "string"
+    },
+    "payment_intent": {
+      "additionalProperties": true,
+      "description": "Exact quote and recipient details when payment is required.",
+      "type": "object"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "description": "Public receipt metadata when the request completes.",
+      "type": "object"
+    },
+    "result": {
+      "additionalProperties": true,
+      "description": "Service result when the request completes immediately.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Request status, commonly awaiting_payment or completed.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / payment_mode

Added value: +{
+  "default": "direct",
+  "description": "Select privatepay only when the PrivatePAY x402 status is enabled.",
+  "enum": [
+    "direct",
+    "privatepay"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / service_id / enum

Previous value: -[
-  "verify.deep",
-  "token.intelligence",
-  "risk.score",
-  "wallet.intelligence",
-  "contract.inspect",
-  "launch.check",
-  "market.snapshot",
-  "research.asset",
-  "research.wallet",
-  "contract.explain",
-  "transaction.explain",
-  "anomaly.detect",
-  "agent.research.report",
-  "portfolio.intelligence",
-  "swap.quote",
-  "transaction.simulate",
-  "decision.context",
-  "github.repository",
-  "forensics.trace",
-  "agent.match",
-  "sponsored.discovery",
-  "intelligence.synthesize"
-]New value: +[
+  "verify.deep",
+  "token.intelligence",
+  "risk.score",
+  "wallet.intelligence",
+  "wallet.bot.classify",
+  "contract.inspect",
+  "launch.check",
+  "market.snapshot",
+  "research.asset",
+  "research.wallet",
+  "contract.explain",
+  "transaction.explain",
+  "anomaly.detect",
+  "agent.research.report",
+  "portfolio.intelligence",
+  "swap.quote",
+  "transaction.simulate",
+  "decision.context",
+  "github.repository",
+  "forensics.trace",
+  "agent.match",
+  "sponsored.discovery",
+  "intelligence.synthesize"
+]

Changed1 schema field changedOct 11, 2026

addedInput schema / properties / pdao_access

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional signed PDAO holder challenge from /api/access/challenge.",
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "signature": {
+      "type": "string"
+    },
+    "wallet": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "wallet",
+    "message",
+    "signature",
+    "nonce"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / service_id / enum

Previous value: -[
-  "verify.deep",
-  "token.intelligence",
-  "risk.score",
-  "wallet.intelligence",
-  "contract.inspect",
-  "launch.check",
-  "market.snapshot",
-  "research.asset",
-  "research.wallet",
-  "contract.explain",
-  "transaction.explain",
-  "anomaly.detect",
-  "agent.research.report",
-  "portfolio.intelligence",
-  "swap.quote",
-  "transaction.simulate",
-  "decision.context",
-  "forensics.trace",
-  "agent.match",
-  "sponsored.discovery",
-  "intelligence.synthesize"
-]New value: +[
+  "verify.deep",
+  "token.intelligence",
+  "risk.score",
+  "wallet.intelligence",
+  "contract.inspect",
+  "launch.check",
+  "market.snapshot",
+  "research.asset",
+  "research.wallet",
+  "contract.explain",
+  "transaction.explain",
+  "anomaly.detect",
+  "agent.research.report",
+  "portfolio.intelligence",
+  "swap.quote",
+  "transaction.simulate",
+  "decision.context",
+  "github.repository",
+  "forensics.trace",
+  "agent.match",
+  "sponsored.discovery",
+  "intelligence.synthesize"
+]

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties

Added value: +{
+  "input": {
+    "description": "Service-specific JSON input.",
+    "type": "object"
+  },
+  "service_id": {
+    "enum": [
+      "verify.deep",
+      "token.intelligence",
+      "risk.score",
+      "wallet.intelligence",
+      "contract.inspect",
+      "launch.check",
+      "market.snapshot",
+      "research.asset",
+      "research.wallet",
+      "contract.explain",
+      "transaction.explain",
+      "anomaly.detect",
+      "agent.research.report",
+      "portfolio.intelligence",
+      "swap.quote",
+      "transaction.simulate",
+      "decision.context",
+      "forensics.trace",
+      "agent.match",
+      "sponsored.discovery",
+      "intelligence.synthesize"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "service_id"
+]
```

Changed2 schema fields changedSep 21, 2026

removedInput schema / properties

Removed value: -{
-  "input": {
-    "description": "Service-specific JSON input.",
-    "type": "object"
-  },
-  "service_id": {
-    "enum": [
-      "verify.deep",
-      "token.intelligence",
-      "risk.score",
-      "wallet.intelligence",
-      "contract.inspect",
-      "launch.check",
-      "market.snapshot",
-      "research.asset",
-      "research.wallet",
-      "contract.explain",
-      "transaction.explain",
-      "anomaly.detect",
-      "agent.research.report",
-      "portfolio.intelligence",
-      "swap.quote",
-      "transaction.simulate",
-      "decision.context",
-      "forensics.trace",
-      "agent.match",
-      "sponsored.discovery",
-      "intelligence.synthesize"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / required
```
Removed value: -[
-  "service_id"
-]
```

First observedSep 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds real value beyond annotations: the no-spend guarantee ('This call never spends funds') is a critical safety clarification for a tool that looks like a purchase, and the branching between immediate execution and a quote-first intent clarifies non-idempotent behavior. Annotations only say readOnly=false, destructive=false, idempotent=false; the description explains what actually happens to funds and what comes back.

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?

Three sentences, each earning its place: purpose, routing prerequisites, mode semantics, and the safety guarantee. The no-spend reassurance is placed where a cautious agent will see it before committing.

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?

With an output schema present, the description only needs to frame the return shape, which it does ('immediate result or exact quote-first payment intent'). The mutation semantics, prerequisites, and no-spend guarantee make it callable without opening other docs; only the optional pdao_access challenge path is left entirely to the schema.

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%, so baseline is 3; the description goes beyond it by explaining what payment_mode values actually cause (PrivatePAY flow vs ordinary USDC) and by framing the returned quote as an input to a separate payment tool. It does not explain pdao_access or the service-specific input object, but those are adequately covered in the schema.

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?

States a specific verb and resource ('Create a selected paid PrivateDAO capability request') and names the outcome shape (immediate result vs quote-first payment intent). It distinguishes itself from catalog/discovery siblings by naming discover_agents and list_catalog as prerequisites rather than substitutes.

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?

Gives an explicit ordering rule ('Use discover_agents or list_catalog first') and a decision rule for the mode parameter (privatepay starts the PrivatePAY flow, direct uses ordinary USDC), plus a follow-up pointer to 'the matching payment tool'. It lacks an explicit when-not / failure-case statement, but the routing guidance is clear.

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 Service Request

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources