Receipt Sequential Checkpoint Validity
Resume checkpoint audit tests whether a claimed prefix is fully covered by confirmed receipts. Use it when an agent needs a verifiable sequential restart offset.
POST https://format.halowerk.com/v1/receipt-sequential-checkpoint-validity
0.005 USDC on Base · payTo 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E
Status: verified · payable
Operator badge: embed this endpoint's live status badge — it reads "Verified Payable" only while the probe record backs it.
Settlement: direct to the seller's payTo — 0% HIVE402 take
Payment routes
{
"checkpoint": 192,
"ranges": [
[
0,
127
],
[
256,
383
],
[
64,
191
]
],
"size": 2501504
}{
"data": {
"unsupported_prefix_bytes": 0,
"valid": true,
"verified_prefix_bytes": 192
},
"limitations": "Local calculation over caller-supplied inclusive byte ranges for one unchanged representation. Receipt order is used only for replay.",
"measured_at": "2026-11-19T11:01:18.988Z",
"source": {
"reference": "https://www.rfc-editor.org/rfc/rfc9110#section-14",
"retrieved_at": "2026-11-19T11:01:18.988Z"
}
}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
Agent intel 
| Trust score | pending / 100 · breakdown |
|---|---|
| Probe uptime (30d) | — over 0 probes · daily |
| Avg 402 latency | — ms |
| Paid calls (30d, on-chain) | 0 calls · 0 buyers |
How to call
POST https://format.halowerk.com/v1/receipt-sequential-checkpoint-validity · input in body · spec from live-challenge
Input schema
{
"type": "object",
"properties": {
"size": {
"type": "integer",
"minimum": 1,
"maximum": 1099511627776
},
"ranges": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": "integer",
"minimum": 0,
"maximum": 1099511627775
},
"maxItems": 2,
"minItems": 2
},
"maxItems": 300,
"minItems": 0
},
"checkpoint": {
"type": "integer",
"minimum": 0,
"maximum": 1099511627776
}
},
"required": [
"size",
"ranges",
"checkpoint"
],
"additionalProperties": false
}Output schema
{
"type": "object"
}curl -i -X POST 'https://format.halowerk.com/v1/receipt-sequential-checkpoint-validity' \
-H 'content-type: application/json' -d '{"size":2501504,"ranges":[[0,127],[256,383],[64,191]],"checkpoint":192}'
Agents: POST https://hive402.scriptmasterlabs.com/mcp → route_task / proxy_call · SDK /sdk/hive402.mjs