ChainAim Outcome AI

Pay for verified outcomes, not tokens.Private by design.Proven on NEAR.

Regulated businesses need intelligence from large volumes of sensitive data, but frontier AI asks them to trust it with their data, their numbers and their budget. Outcome AI replaces that trust with proof. Your files and their rows stay on your PC; only masked text goes to an attested NEAR AI enclave; the agent pays on NEAR before the work, and gets its money back automatically if privacy is not proven. Press Play to hear a real run, step by step (NEAR testnet, 14 Nov 2026): run A in 10 steps (tenant t02, with one counter-offer, job 0ed4fe96…), run B (refund) in 4.

TENANT'S PRIVATE RUNTIME · the tenant's machine · data stays here CHAINAIM CONTROL PLANE · own project, own keysHackathon: own container on tenant machine · later: hosted NEAR AI · confidential computing (TEE) NEAR TESTNET · public chain CHAINAIM DATA PLANEDocker · ports on 127.0.0.1 only ask price · quote · mandate check · receipt signed payment settle USDC first (relayer pays gas) run exact query rows stay here question + table masked bytes call evidence verify report refund USDC ids + hashes only read the payment Tenant's AI agentca-agent · tenant keyspolicy · signs mandate + payment Console + APItab 03 · holds question + resultruns only within signed limits Your filesbank statement, invoices, billsread-only, never uploaded Analystexact SQL on your filesdeterministic result table Gateway + Presidiomasks personal datahashes the bytes it sends Paywall (x402)settles the NEAR paymenton the PC today · moves off it next ca-attestchecks NEAR AI's attestationno verdict, no delivery ChainAim signerAP2 quote + signed limits · mandate checksigned receipt · automatic refundssees ids, sizes, hashes, amountsnever a question, row or answer NEAR AI model in a TEEdeepseek-v4.1-flash · cloud-api.near.aisigned attestation report(Intel TDX + NVIDIA GPU) NEAR testnetUSDC ft_transfer to ChainAim (pay)USDC ft_transfer back (refund)public: payer, amount, timeno question, no data, no answer Ops view: near-watch + admin UIjob ids, hashes, payments, attestations Anyone, offline: verify-receipt · observe-receiptno keys, no account: pinned public keys + the chain

Who sees what

PartySeesNever sees
Tenant's private runtime (ChainAim data plane)Your files, the rows, the question and the answerChainAim's signing keys (-Planes checks every container)
ChainAim's signer (control plane)Job ids, file sizes, hashes, prices, the mandate, the paymentThe question, SQL, rows or answer (the signer refuses unknown fields by name)
NEAR AI (TEE)The masked question and result table, inside an attested enclaveYour files; unmasked personal data
NEAR chain (anyone)Who paid, how much, when; a refund if there was oneAny content: only the payment is on NEAR

Narration uses your browser’s built-in voices. The smoothest are the “Natural” voices in Microsoft Edge on Windows (Indian English: Neerja, Prabhat; US English: Aria, Guy). Chrome offers Google voices.

Tenant's private runtime: the tenant's machine runs its own AI agent, its files and the ChainAim data plane (console, analyst, gateway with Presidio, ca-attest and the paywall), all in Docker on 127.0.0.1. ChainAim signer and control plane: for the hackathon a separate container (its own Docker project and keys) on the same tenant machine, so the separation is by design, not by hardware. Next: ChainAim hosts the signer and control plane (cloud, then a TEE), and the paywall with its relayer key moves there too.

Demo and proof links

Run it, see it

Rules for judges

  1. No keys, no account, no install: Node.js 22.22+ and the repository.
  2. Run verify-receipt on docs/judge/sample-receipt-2026-11-14T0729Z.json: expect four OK lines (receipt, money trail, attestation, egress) and "counter of".
  3. Run observe-receipt: the same payment, read from NEAR.
  4. The Docker stack is optional; the video shows it running.

Built to extend

Modular by design: the data plane, ChainAim's control plane and settlement are separate services with signed, allow-listed interfaces. After the hackathon they move into dedicated cloud services, then into TEE workloads (NEAR AI / Shade Agents or Phala Cloud), with full ZK-PRET integration for verifiable trade-finance outcomes.

Check it yourself

node scripts/verify-receipt.ts --file <receipt.json> checks the receipt, the signed quote and limits, the agent's mandate, the money trail, the attestation bundle and the egress line offline, against public keys pinned in the repository. node scripts/observe-receipt.ts --file <receipt.json> reads the same payment from NEAR testnet. Run A's transaction: 8E6mhkZP… on nearblocks.