Move public evidence
with the workflow.
A reset headline is easy to copy and hard to audit. The Verified Reset Packet gives a developer tool one public signal, one SHA-256 receipt, and one explicit boundary so the evidence can travel without private credentials.
curl --fail --silent https://lydiahub.online/api/verified-packetParse the packet, verify the receipt, then decide how your own tool should display a public signal. The response is safe to fetch cross-origin and is designed for polling with ETag revalidation.
Fetch one packet
Read the current public signal and its integrity receipt in one credential-free request. No account session, cookie, or quota value is involved.
Verify before rendering
Check the SHA-256 receipt and the public boundary before your tool displays or forwards the result. A check time is not a reset claim.
Relay useful proof
Add a badge, evidence link, or machine check to the surface where your users already work. Keep your private quota logic separate.
Minimal verification check
curl --fail --silent https://lydiahub.online/api/verified-packet | jq -e '.boundary.credentialsRequired == false and (.receipt.value | startswith("sha256:"))'README-ready relay
[](https://lydiahub.online/proof-packet)Add the badge or link to a repository, dashboard, or community page where the public context is useful. The destination explains the evidence rather than presenting a generic daily poster.
Keep the two jobs separate
Public evidence
ResetPulse reports what a public source says, when the monitor observed it, the stated scope, and whether the record has a receipt.
Private account state
Your own tracker or Codex surface answers what one account shows. ResetPulse never asks for that login or attempts to replace it.
Start with the contract
Use the Verified Reset Packet, inspect the schema, or open the full integration guide. For collection evidence, read the public reliability report.