Private AI · hardware attestation · NEAR

Check that an AI answer really came from a sealed model.

Confidential AI runs inside a hardware enclave that signs what it is. Attested turns that evidence into a receipt anyone can re-check offline, and anchors the receipt's hash on NEAR.

1. AskSend a sensitive document to a model on NEAR AI Cloud's confidential tier.

2. ReceiptGet the answer plus a receipt: hashes, the enclave's Intel and NVIDIA evidence, every check labelled.

3. VerifyA third party re-derives it all from the file, offline. One changed byte fails it.

Verify it yourself

Paste or drop a receipt.json. Everything runs in this page, in your browser, with no network. Nothing is uploaded.

Drop receipt.json here Choose a file

or paste the JSON

What a receipt does and does not prove

Verified here, with real cryptography

Intel TDX quote signature chains up to Intel's pinned root
The enclave's signing key and our nonce sit inside the signed quote
The boot log replays to the measured registers
NVIDIA's signed verdict for 8 GPUs, bound to the same nonce
The receipt's own hashes: change one byte and it fails

Not proven (and labelled that way)

Intel TCB status and revocation (needs Intel collateral)
That the published software is the audited build
Streaming answers (signed by the gateway, not the model)
That the answer is correct
The browser cannot re-check the secp256k1 response signature; the CLI does

Attested: verifiable receipts for private AI on NEAR. MIT licensed. Code written with AI assistance.sample = recorded demo receipt