Wisely x402 Agent-Payment Infrastructure

x402_endpoint_secret_settings

Explain how endpoint-scoped encrypted secrets are added and listed by name without returning secret values.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No
`type`	No
`asset`	No
`input`	No	Public-safe request body/input for a hosted service or endpoint. Never include secrets, raw cards, wallet keys, passwords, or private account tokens.
`items`	No
`query`	No
`since`	No
`itemId`	No
`accepts`	No
`content`	No	Public-safe creator content for preview/import. Do not include secrets, private student data, or copyrighted material you do not own.
`network`	No
`audience`	No	Optional audience hint for wisely_start_here / wisely_get_playbook / wisely_agent_instructions.
`payoutId`	No
`platform`	No	Optional OS/platform hint for local bridge setup, e.g. windows, mac, linux.
`amountUsd`	No
`creatorId`	No
`fromAsset`	No
`localPort`	No	Optional localhost port for the local commerce bridge MCP server. Defaults to 4027.
`receiptId`	No
`sellerUrl`	No	Third-party x402 paid resource URL to probe for HTTP 402 payment requirements.
`serviceId`	No
`sessionId`	No	Wallet handoff/payment session id returned by x402_wallet_handoff/connect_wallet.
`toAddress`	No
`sellerBody`	No	Public-safe POST body for an external x402 seller. Never include cookies, bearer tokens, wallet secrets, private keys, card data, or account passwords.
`contentType`	No
`fromAddress`	No
`fromNetwork`	No
`manifestUrl`	No
`paidActions`	No
`endpointSlug`	No
`sellerMethod`	No	Use POST for paid APIs that need a public-safe body before returning 402.
`payoutAddress`	No
`serverJsonUrl`	No
`idempotencyKey`	No	Stable retry key for paid invokes and wallet handoff sessions.
`paymentPayload`	No
`includeExamples`	No	Set false to request a shorter playbook response.
`fromTokenAddress`	No
`preferredNetwork`	No	Preferred payment network for wallet handoff, e.g. eip155:8453 or base.
`defaultEntitlement`	No
`paymentRequirement`	No
`paymentRequirements`	No
`returnSignedPayment`	No	Alias for includeSignedPayment.
`includeSignedPayment`	No	For x402_payment_session_status, include the signed X-PAYMENT payload when the user has signed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / properties / localPort

Added value: +{
+  "description": "Optional localhost port for the local commerce bridge MCP server. Defaults to 4027.",
+  "type": "number"
+}

addedInput schema / properties / platform

Added value: +{
+  "description": "Optional OS/platform hint for local bridge setup, e.g. windows, mac, linux.",
+  "type": "string"
+}

Changed8 schema fields changedMay 27, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Stable retry key for paid invokes and wallet handoff sessions.",
+  "type": "string"
+}

addedInput schema / properties / includeSignedPayment

Added value: +{
+  "description": "For x402_payment_session_status, include the signed X-PAYMENT payload when the user has signed.",
+  "type": "boolean"
+}

addedInput schema / properties / input

Added value: +{
+  "description": "Public-safe request body/input for a hosted service or endpoint. Never include secrets, raw cards, wallet keys, passwords, or private account tokens.",
+  "type": "object"
+}

addedInput schema / properties / paymentPayload
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / paymentRequirements
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / preferredNetwork

Added value: +{
+  "description": "Preferred payment network for wallet handoff, e.g. eip155:8453 or base.",
+  "type": "string"
+}

addedInput schema / properties / returnSignedPayment

Added value: +{
+  "description": "Alias for includeSignedPayment.",
+  "type": "boolean"
+}

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Wallet handoff/payment session id returned by x402_wallet_handoff/connect_wallet.",
+  "type": "string"
+}

Changed2 schema fields changedMay 27, 2026

addedInput schema / properties / audience

Added value: +{
+  "description": "Optional audience hint for wisely_start_here / wisely_get_playbook / wisely_agent_instructions.",
+  "enum": [
+    "agent",
+    "builder",
+    "creator",
+    "operator",
+    "indexer"
+  ],
+  "type": "string"
+}

addedInput schema / properties / includeExamples

Added value: +{
+  "description": "Set false to request a shorter playbook response.",
+  "type": "boolean"
+}

Changed5 schema fields changedMay 25, 2026

addedInput schema / properties / content

Added value: +{
+  "description": "Public-safe creator content for preview/import. Do not include secrets, private student data, or copyrighted material you do not own.",
+  "type": "string"
+}

addedInput schema / properties / contentType

Added value: +{
+  "enum": [
+    "markdown",
+    "csv",
+    "json"
+  ],
+  "type": "string"
+}

addedInput schema / properties / defaultEntitlement

Added value: +{
+  "enum": [
+    "free",
+    "subscriber",
+    "paid"
+  ],
+  "type": "string"
+}

addedInput schema / properties / items
```
Added value: +{
+  "type": "array"
+}
```
addedInput schema / properties / paidActions
```
Added value: +{
+  "type": "array"
+}
```

Changed3 schema fields changedMay 24, 2026
- addedInput schema / properties / creatorId
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / itemId
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / query
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / properties / sellerBody / description

Added value: +"Public-safe POST body for an external x402 seller. Never include cookies, bearer tokens, wallet secrets, private keys, card data, or account passwords."

addedInput schema / properties / sellerMethod / description

Added value: +"Use POST for paid APIs that need a public-safe body before returning 402."

Changed12 schema fields changedMay 21, 2026

addedInput schema / properties / accepts
```
Added value: +{
+  "type": "array"
+}
```
addedInput schema / properties / asset
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / endpointSlug
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / network
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / paymentRequirement
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / payoutAddress
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / payoutId
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sellerBody
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / sellerMethod

Added value: +{
+  "enum": [
+    "GET",
+    "POST"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sellerUrl

Added value: +{
+  "description": "Third-party x402 paid resource URL to probe for HTTP 402 payment requirements.",
+  "type": "string"
+}

addedInput schema / properties / since
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```

AddedMay 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The description adds a safety-relevant behavioral trait (does not return secret values), but with empty annotations, it lacks broader behavioral disclosure such as read-only guarantees, authentication requirements, or side effects. Some credit for the safety note, but not enough context.

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?

Single sentence, no filler, immediately states purpose. The description is concise and well-structured.

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

Completeness2/5

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

Despite the complexity (43 params, no output schema, no annotations), the description provides only a minimal statement. It doesn't explain invocation inputs, output format, or edge cases, leaving significant gaps for an agent to use it effectively.

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

Parameters1/5

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

With 43 parameters and only 33% schema coverage, the description offers no mapping or hint about which parameters are relevant. Users are left without guidance on how to invoke this tool, and the description does not compensate for the undocumented schema.

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?

The description clearly states the tool's function with a specific verb ('Explain') and resource ('endpoint-scoped encrypted secrets'), and specifies the scope (added/listed by name without returning values). This distinguishes it from sibling endpoint tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any mention of required context or prerequisites. The description only states what the tool does, not when to reach for it.

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

All Wisely x402 Agent-Payment Infrastructure 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.

x402_endpoint_secret_settings

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources