What the AI read
On chain
- Press the button in step 03. The contract's answer lands here, with its receipt and transaction.
ready.
Pick an invoice. Check the AI's signed reading in your own browser. Then let an agent send it to a NEAR contract and watch who decides. Every button sends a real testnet transaction. No wallet, no terminal.
ready.
Upload a PDF. This browser reads it and checks every line for ink, so text no person can see never reaches the AI. The visible text goes to Clear to Pay's reader running inside OutLayer's sealed machine (Intel TDX), with NEAR AI's private model. The reading comes back signed by a key that exists only in that machine, and this page checks it.
Use a sample or a fake invoice. Over HTTPS OutLayer keeps only hashes, but don't upload real company documents to a hackathon demo.
No PDF to hand? Download a sample: clean · poisoned (white text)
The reading, its checks and who the contract would pay appear here.
A static page has nowhere to hide a key, so Judge mode publishes one: agent.json. NEAR itself limits what it can do. It may call two methods on one demo contract, attach no money, and burn a small gas allowance. Take it and try. The contract still pays only the supplier's registered address, only for signed deliveries, only once.
The live contract, guard.cleartopay.testnet, and its pool are never touched here. Judge mode runs the same code on its own account.