Wisely x402 Agent-Payment Infrastructure

x402_builder_payouts

Read/update payout settings and create manual payout request packets without moving funds.

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.

TDQS

A3.5/5.0

Behavior3/5

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

With empty annotations, the description carries the full burden. It discloses a key behavioral trait—'without moving funds'—which is valuable safety-related context. However, it does not detail side effects, permissions, reversibility of updates, or the nature of 'payout request packets.'

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?

The description is a single, tightly worded sentence that front-loads the primary actions and includes a critical qualifier. There is no fluff or repetition.

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?

Given the tool's complexity (43 parameters, nested objects, no output schema, no annotations), the description is far too sparse. It fails to explain what 'payout settings' include, what 'manual payout request packets' are, how the tool is invoked, or what the response looks like.

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

Parameters2/5

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

Schema description coverage is only 33%, and the tool description does not compensate by explaining any of the 43 parameters. Many generic parameters like 'url', 'type', 'items', and 'query' are left ambiguous, and the description adds no meaning beyond the 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: 'Read/update payout settings and create manual payout request packets without moving funds.' This uses specific verbs and a clear resource, and the qualifier 'without moving funds' distinguishes it from fund-moving tools among its siblings.

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

Usage Guidelines3/5

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

The description implies the tool is for managing payout settings and creating payout request packets, but it does not explicitly state when to use this tool versus alternatives, nor does it name any sibling tools or provide exclusions beyond the 'without moving funds' qualifier.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.5/5.0

Disambiguation1/5

The tool set is riddled with aliases and duplicates (e.g., start_here, wisely_start_here, get_playbook, agent_instructions, readme, wisely_get_playbook, wisely_agent_instructions all serve the same purpose). Dozens of status tools and setup aliases overlap heavily, making it nearly impossible for an agent to select the right tool without testing.

Naming Consistency2/5

There is a mix of x402_ and wisely_ prefixes, plus unprefixed generic tools like start_here, connect_wallet, and readme. Alias names diverge from their canonical names (e.g., connect_wallet vs x402_wallet_handoff), and while snake_case is consistent, the pattern is not predictable across the full set.

Tool Count1/5

65 tools is far beyond what is typically appropriate for an MCP server (3-15). The count is inflated by aliases and many near-identical status/check tools, creating a bloated surface that is unnecessarily heavy and confusing for agents.

Completeness3/5

Core payment, wallet, receipt, and quote workflows are well covered. However, there are significant gaps in actual builder endpoint management (only handoff instructions, no direct create/update/delete tools) and creator catalog lifecycle (preview and onboarding handoff but no publish/update/delete tools), leaving some workflows as dead ends.

x402_builder_payouts

Input Schema

TDQS

Glama MCP Gateway

TDQS

Resources