← Market · Board · Updates · Notifications · Verified Payable Index · Independent Volume · Digital Store

Paid-delivery method

How the Paid-Verified board and the deliveredAfterPayment field on every HIVE402 listing are produced — and the limits of what they claim. The same content is served as JSON at /paid/method.json.

What a paid check is

A paid check is one real purchase: HIVE402 paid one named route from the fleet proof wallet (0x2DfFAdAB1A1b6B0FDeFBD78ABE56EbFa118db56D on Base), at the price the endpoint challenged live — never above the listed price, never above the per-check cap — calling it the way the seller declared (method, URL and input from the endpoint's own captured call spec or example). The verdict required BOTH the settlement transaction (from the PAYMENT-RESPONSE receipt, or recovered from the on-chain USDC transfer log and verified) AND the response that came back. A challenge alone is never a verdict.

Verdict definitions

OutcomeMeaning
settled_usableSettled + usable response — the only outcome that counts as delivered.
failed_paid_then_402Payment submitted, endpoint answered 402 again. Whether it also settled is recorded separately on the check — a 402 after submission that never charged is a different fact from one that kept the money.
failed_error_statusPaid call returned an error status.
failed_empty_bodyPaid call returned 2xx with an empty body.
failed_junkPaid call returned an error payload instead of product.
failed_no_response / paid_no_responseThe paid request produced no response at all. Recorded as failed_no_response when nothing settled, and as paid_no_response when the payment settled on-chain but no product came back.
transport_error_after_signPaid request failed in transport after signing — settlement is checked on-chain before the check is scored either way; a paid request is never retried blind.
probe_errorProbe-side error — never scored against the seller.

Failures are published as failures, with the same prominence mechanics as successes: paid-then-402, error status, empty body, junk payload and no-response outcomes appear in the check history on the board's dataset (/paid.json), in each endpoint's deliveredAfterPayment record, and in the run numbers below. A board that only publishes wins is exactly the fake this product exists to replace.

A canary is not a guarantee

A canary is not a guarantee. A dated check proves what happened on that date, on that route, for that input. It does not prove the next call, a different route on the same listing, or a different input.

A check covers the route paid — the resource URL, network, asset, payTo and price as challenged live at check time. A listing with several payment routes is checked per route; one route's record says nothing about the listing's other routes.

SELF-PROOF

SELF-PROOF labeling: ScriptMasterLabs' own endpoints are proven by ScriptMasterLabs paying itself end-to-end. They are labeled SELF-PROOF everywhere the record appears, and they are never blended into outside numbers — not in board counts, not in any rate, not anywhere.

Sample honesty

Sample honesty: a delivery rate always travels with its sample size and its last-check date. 1 of 1 is shown as "1 of 1", never dressed up as "100% reliable." An endpoint with no paid check carries no rate at all — the field is null, and surfaces say "no paid-delivery record yet." Absence is stated, never silently zero-filled.

No pay-to-play

No pay-to-play: sellers cannot buy a check, a verdict, or a rank. Checks are run by HIVE402's weekly canary on its published selection rule, or bought by buyers about routes they are considering — and the outcome publishes either way. The trust score's formula contains no delivery component and no paid component; deliveredAfterPayment is evidence displayed next to the score, never folded into it.

How routing uses the record

· Tie-break / preference among near-equals: in /api/route, a candidate with a delivered record is preferred over one with no record when their route scores are within 0.02 of each other.

· Failed-delivery demotion: a candidate whose most recent paid check failed delivery is demoted below delivered and unrecorded candidates alike.

· The search quality formula (0.45·trust + 0.25·demand + 0.15·latency + 0.15·price) has no paid component, and the trust score does not absorb the delivery rate. Nobody — not a seller, not a check buyer — can spend money and move either number.

Canary selection

Canary selection, weekly: ~30 Base USDC exact endpoints priced at or below $0.01, all currently challenge-verified payable — route winners (the listings /api/route actually returns for common buyer tasks, plus the most-called in the proxy log), the highest on-chain paid demand (paidCalls30d, self-pay excluded), and a rotating sample (never-yet-checked first, then oldest-check-first). At most 3 checks per operator per run. ScriptMasterLabs' own endpoints are never in the outside canary; they are re-proven on the SELF-PROOF track. Per-run spend is hard-capped at $0.35 from the fleet proof wallet; authorizations count against the cap at submission, settled or not.

The latest canary run, in numbers

Run canary-2026-11-18 — checks dated 2026-11-18; this dataset regenerated 2026-11-19. Every number below is computed from the fleet paid-probe log (paid-probes.json) by the dataset builder — never hand-typed.

Paid checks attempted30
Delivered (settled + usable response)16 of 30
Failed14 of 30
— no response to the paid call12 (11 never settled, $0 lost · 1 settled and delivered nothing, $0.001 lost)
— error status2 (0 settled)
— paid-then-4020
— empty body0
— junk / error payload0
Total USDC spent (settled)$0.05

Across the whole probe log to date: 31 paid checks of outside endpoints (1 standalone probes outside the weekly runs), 17 delivered, $0.052 settled in total.

Script Master Labs LLC · SDVOSB · Kinston, NC · Terms · Refunds · Privacy · Contact

SML network: ScriptMasterLabs — the main site · SML Dual Market — the human storefront · VA Ratings — VA disability ratings, free for veterans