x402r-dispute_skill

This skill helps you file and track x402r payment disputes on the refundable payments protocol, simplifying evidence submission and status updates.

Python

2.5k

GitHub Stars

8

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill x402r-dispute

_meta.json447 B
clawhub.json640 B
e2e-test.ts13.4 KB
package-lock.json25.6 KB
package.json930 B
pnpm-lock.yaml15.5 KB
SKILL.md2.5 KB
tsconfig.json457 B

Overview

This skill files and tracks payment disputes on the x402r refundable payments protocol. It provides a CLI to create on-chain refund requests, submit evidence, query dispute status, list disputes, view evidence, and verify arbiter rulings. The tool saves local state so follow-up commands work without re-supplying payment data.

How this skill works

The CLI signs and submits refund requests to the PaymentOperator contract and posts evidence to an arbiter server (optionally pinned to IPFS). Status checks query the arbiter first and fall back to on-chain data when possible. The verify command replays the arbiter's AI evaluation to confirm commitment hashes and the decision were produced deterministically.

When to use it

You paid a 402 refundable payment and want to request a refund
You need to submit structured evidence for a disputed payment
You want to monitor dispute resolution status and view submitted evidence
You must verify the arbiter's AI ruling and its cryptographic commitment
You want a CLI workflow that stores last dispute state locally for convenience

Best practices

Configure wallet, operator address, arbiter URL, network, and optional RPC before running commands
Fund the configured wallet with native ETH for gas and token used for payments (testnet faucets for testing)
Use --payment-json or run an initial dispute to save state; subsequent commands will reuse saved state
Include structured evidence with --file for reproducible records and easier arbiter review
Use verify only when the arbiter server is accessible; it has no on-chain fallback

Example use cases

File a refund request after receiving poor service from a 402 payment-enabled merchant
List and filter disputes for a marketplace operator to audit recent refund requests
Show full evidence envelope (payer, merchant, arbiter) when preparing for on-chain appeals
Verify the arbiter AI decision integrity after a ruling is returned
Run quick tests against the provided Sepolia test merchant and arbiter during integration

FAQ

No. The CLI saves the last-dispute state after filing a dispute. Provide --payment-json only if no saved state exists or you want to query a different payment.

What happens if the arbiter server is down?

Status and show commands fall back to on-chain queries when possible. List and verify rely on the arbiter server; verify will fail without it.