Result validation check
wever_result-validation-checkAgent Purchases: submit the order’s own terms for one paid call (the values it asked for, the fields a delivered result carries, what counts as delivered, how fresh the data must be and the fewest items that count) and the result that came back (HTTP status, its fields with their values, its item count, when its data was current, when it arrived and any error carried in its body). The signed report checks each term met, not met or unstated and names every failure: a non-2xx status, an error inside a success, a requested value the result carries differently, a required field it lacks, an empty or short result and stale data. A 200 response carrying the wrong data is reported as a silent failure, not a success. A job’s work against acceptance criteria is wever_deliverable-check and a result that never arrived after payment is wever_payment-recovery-check. Verdict silent_failure, order_not_met, validation_unverified or order_met. POST /api/result-validation-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-purchases-contract. Human page: https://weverlabs.com/agent-purchases/.
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": {
"order": "<order>",
"result": "<result>"
},
"name": "wever_result-validation-check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| label | No | Optional name recorded in the report. | |
| order | Yes | ||
| result | Yes |