Check one PCoC CBOR object. Two readings, never mixed: checks (did the sampled walk reproduce?) and policy (does this Grounding Lab instance accept it?). Checks can pass while policy still rejects.
Verification only. Passing here does not sign you in, grant a badge, or
show that you produced the file — anyone holding the bytes can run this.
One object per check, at most 2 MiB, .cbor.
You do not need to produce an object. Download one, or check it from this page. Labels are what the live bench returned on 2026-09-21.
Checks should pass. Policy should reject — too small for Grounding Lab
accept (3 gaps / 4 MiB vs ≥18 / ≥256 MiB). Under a second.
waypoints_registered is unmeasured on this bench; that is
not a failed check.
Checks should pass (~45 s). Policy should accept the rows it can measure (18 gaps, 256 MiB). The reading stays incomplete because this bench does not check waypoint registration — not “the object failed waypoints.”
Drop one .cbor file here, or pick one.
The page is static; the walk runs on the bench, not in this tab.
Production default is https://verify-api.pcoc.app. Point this
at a local bench with ?api=http://127.0.0.1:8787 when running
the service yourself.
Claiming an object as its producer is Admit as owner. The walk runs on the gl-verify API, not in this tab.