dispute_packet_packet
$0.05 USDC on Solana per packet - the payment buys one signed dispute-evidence packet for the one paid call you name: the terms as quoted in the captured challenge, the payment as settled on-chain (verified under settlement-evidence/v1), the delivery artefact exactly as submitted with its service-computed body hash, timestamps, and an empty reverse-transaction field. The delivery leg is BUYER-SUBMITTED - NOT VERIFIED; the PAYMENT-RESPONSE header is UNSIGNED and stated so; adjudication is NOT offered.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"challenge": "<challenge>",
"paymentResponse": "<paymentResponse>",
"delivery": "<delivery>"
},
"name": "dispute_packet_packet"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| delivery | Yes | The delivery artefact AS RECEIVED: {status (integer 100-599), body (string) } or {status, bodyHash (64-hex SHA-256)} - exactly one of body / bodyHash. Buyer-submitted evidence, NOT verified by this service. | |
| challenge | Yes | The captured 402 challenge object exactly as issued for the paid call being packeted. Processed in memory only, never stored. | |
| timestamps | No | Optional timestamps object {challenged_at?, paid_at?, delivered_at?}. | |
| paymentResponse | Yes | The PAYMENT-RESPONSE header value from the paid call (base64 JSON string; a raw JSON string or the decoded object are also accepted). Processed in memory only, never stored. | |
| settlementSignature | No | Optional explicit settlement reference (the settlement transaction signature). When absent, the header's transaction field is the settlement reference. |