# gov.halowerk.com Snapshot Verify

> gov.halowerk.com Snapshot Verify is a paid API for AI agents from gov.halowerk.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-16).

Sorts unique scalar key/value entries, computes a canonical SHA-256 digest, and optionally verifies it against a claimed hash

## Facts

- Endpoint: POST https://gov.halowerk.com/v1/snapshot-verify
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gov-halowerk-com-snapshot-verify-01898eb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mnpNP2FJVTUbc5YKiiLJ_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability gov-halowerk-com-snapshot-verify-01898eb7 -d '<json body>'
```

Example prompt: Can you hash these governance snapshot entries — proposalId: 'p-42', status: 'approved', voteCount: 318 — and check whether the result matches the digest a8f3c2d1e9b054...abcd1234 that I have on file?

## When to prefer this

Choose this endpoint when you need a deterministic, canonical SHA-256 fingerprint of a flat key/value dataset and optionally want to verify it against a claimed digest. It is ideal for audit trails, tamper detection, and cross-party data agreement checks on scalar governance or configuration data. It does NOT provide blockchain proof, timestamp attestation, or signer verification — if those are required, use a dedicated notarization or on-chain anchoring service instead.

## Known failure modes

- Duplicate keys in the entries array may cause ambiguous sorting or rejection
- entries array is empty (minItems: 1 violated) — returns validation error
- claimed_sha256 does not match the 64-character hex pattern — returns schema validation error
- entries array exceeds 50,000 items — rejected by schema
- key or value types outside the allowed scalar types (string, number, boolean, null) — rejected
- Payment failure via x402 protocol — endpoint returns 402 and does not process

## How this service works

Sorts unique scalar key/value entries through canonical JSON serialization and computes SHA-256. It verifies byte-level agreement with an optional claimed digest only; it does not prove block inclusion, timestamp, signer identity, or chain consensus.

## Output

Returns the computed SHA-256 hex digest of the canonically sorted and serialized key/value entries. If a claimed_sha256 was provided, also returns a boolean indicating whether the computed digest matches the claimed one byte-for-byte. Does not attest to blockchain inclusion, timestamps, signer identity, or chain consensus.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "entries": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "key",
     "value"
    ],
    "properties": {
     "key": {
      "type": "string",
      "maxLength": 256,
      "minLength": 1
     },
     "value": {
      "type": [
       "string",
       "number",
       "boolean",
       "null"
      ]
     }
    },
    "additionalProperties": false
   },
   "maxItems": 50000,
   "minItems": 1
  },
  "claimed_sha256": {
   "type": "string",
   "pattern": "^[0-9a-fA-F]{64}$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gov-halowerk-com-snapshot-verify-01898eb7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gov.halowerk.com](https://www.zero.xyz/host/gov.halowerk.com/llms.txt)