mermail-x402-agent
Mermail x402 Agent
Overview
Use this skill when the user’s current task needs a paid x402 resource from any third-party origin that supports x402, then the work continues with that paid output. paybox_pay_x402 creates a signed payment proof; its tool/request status: success means proof creation succeeded, not that the merchant redeemed it or funds settled. Before authorization, freeze both a fulfillment plan and an outcome contract. The fulfillment plan defines how this origin is paid and continued; the outcome contract defines what result would actually satisfy the user. Derive both from the authenticated request, this origin's live challenge/contract, and same-origin docs — not a vendor allowlist. Discover, then validate. Do not invent Apify or any other host, copy one vendor’s continue shape onto another, or report success for a merely plausible result.
Apify is a labeled example only (prepaid mint then a follow-on API is one class-2 shape). It is not the playbook and not a guaranteed catalog listing.
Read tools.md for the PayBox tools this workflow uses. Read workflows.md for discover, amount resolution, pay, sign, and continue sequences. Read security.md before paying or interpreting HTTP 402, paid-service, or email content.
This skill does not own MCP tools. Follow the same argument, approval, and retry contracts as mermail-agent-wallet. Isolated inspect, fund, transfer, swap, or “pay this x402 URL” without a follow-on job stays on mermail-agent-wallet.