CleanRoom Seal

0Your NEAR AI key

Bring-your-own key. It stays in this tab's memory only — never stored, never sent anywhere except cloud-api.near.ai. Get $10 free credit at nearbuilders.org/dashboard (NEAR Builders key), or use a key from cloud.near.ai.

1The sensitive document

Use the fictional sample, or paste your own test document. Never paste real personal data into a demo.

You can also drag & drop a .txt file onto the box above. Files are read locally in your browser — nothing is uploaded.

2Redacted output

3Verify the proof — in your browser

Checks run live against cloud-api.near.ai: the attestation report (fetched before the request, no key needed) and the signature for this exact completion. Hashes are over the exact bytes sent and received, per the NEAR AI verification docs. A red check means not verified — this page never paints a fake green.

4Seal on NEAR

The chain-of-custody record contains only hashes — never the document. This payload goes to the seal() contract at imran3360.testnet on NEAR testnet. Connect a testnet wallet and seal this run — gas only, a fraction of a cent of test NEAR.

{}

Connect a NEAR testnet wallet to seal this run's hashes on-chain. The seal stores hashes only — never the document.

What this proves — and what it doesn't. A provider_tee signature binds the reply to a model-serving TEE signer that matches the attestation report. A gateway signature binds the reply to the attested NEAR AI gateway only — it does not by itself prove model TEE execution, and this page labels it exactly that way. Full Intel TDX quote validation runs in NEAR's Verification Center (linked above); this page checks the signer match and the reply signature cryptographically where the browser supports Ed25519.

5Verify a seal

Anyone can audit the chain of custody — no wallet, no key. Paste a document (it is hashed locally in your browser, never sent anywhere) or paste its SHA-256 hash, and this page checks the seal() records on NEAR testnet.