Every GETKINETIK sovereign node can produce hardware-sealed evidence. The bureau publishes what we observe — including an optional reference Genesis Score (0–1000, not a token). Your network's verifier still runs; we're the second read when you want one.
The bureau publishes independent scans using only public APIs and on-chain ledger state — no internal network data, no allegations of intent, just structural patterns.
NO_LOCATION_DATA. Cross-validated against reward history: all correctly zeroed by WXM pipeline — but 16,186 WXM earned before zeroing, devices still registered and counting toward cell capacity.
****0DLF*. Coordinate collision impossible for real hardware. Registration-layer anomaly.
Calibration anchors — partners pick a threshold appropriate to their own fraud cost (e.g. 500 permissive, 750 strict, 900 premium tier).
Five categories. Each is signed evidence the node produced — or signed evidence a partner network reported through a typed attestation channel.
Signature verifies. Node ID matches the public key fingerprint.
Attribution string intact. Failures hard-gate the score to
null.
Chain age (when the first heartbeat was signed) and lifetime beat count. Long, unbroken chains can't be faked.
Light, motion, and pressure sensors must be within physical ranges. Impossible values raise tamper flags.
Partner attestations: did the node perform expected work?
Wired through the /api/attest partner channel.
The L4 earnings ledger: each receipt carries the canonical 1% protocol disclosure fee and verifies against the chain.
One POST /api/verify-device returns identity fields plus a
bureau-signed attestation (verifiable offline with
@getkinetik/verify) and a convenience derived
tier. The bureau ships evidence, not verdicts:
{
"valid": true,
"nodeId": "KINETIK-NODE-CDC262E7",
"pubkey": "ff07e53d…",
"schema": "proof-of-origin:v2",
"attestation": {
"payload": { "v": 1, "kind": "attestation", "…": "…" },
"signature": "<128-char hex bureau Ed25519>",
"hash": "<16-char hex>"
},
"derived": {
"tier": "STANDING",
"score": 636,
"flagged": false,
"flags": [],
"policyVersion": "v2.0.2"
},
"asOf": "2026-05-13T03:00:00.000Z"
}
Why a bureau, not a DIY check ↗ · Interactive API docs ↗ · OpenAPI 3.1 spec ↓ · Postman collection ↓ · Score-change webhooks ↗ · 5-minute guide ↗ · Methodology ↗
A grading bureau that requires you to trust its servers is not a bureau — it's a vendor. Partners who want zero infrastructure dependency can verify every signed proof in-house, with pure math, using the same byte-for-byte cryptographic contract our app uses:
npm install @getkinetik/verify import { verifyArtifact } from '@getkinetik/verify'; const report = await verifyArtifact(signedProof); if (report.valid) { // device is real, signed by a GETKINETIK sovereign node. // no network call to getkinetik.app was made. }
Published 2026-05-13 · npmjs.com/package/@getkinetik/verify ↗ · 27/27 cryptographic smoketests enforced before every publish · MIT licensed · ~36 KB unpacked · two audited noble crypto deps, no DOM, no telemetry, no network.
Charter: NEUTRALITY.md · PRIVACY.md
If you run a DePIN network and want to pilot scoring or wire a partner attestation channel into the bureau, write to eric@outfromnothingllc.com. Pilots are free for the first wave.