Four agents. Four tracks. One verdict. No trade without all four.
Compose a NEAR testnet DeFi intent below. Four AI agents — each running inside its own NEAR AI Cloud TEE, each a different model — judge it in parallel: a contract Auditor, a scam Sentry, a risk Actuary and a privacy Warden. Every verdict is cryptographically verified in your browser (TEE attestation + Ed25519 signature over the exact request/response bytes). Consensus is 4-of-4 APPROVE with verified TEE proofs — or the trade is blocked. Testnet only; funds move only at Step 5 (execution), and only after the sealed on-chain record is re-read as APPROVED.
AI SwarmsAI Security & DefensePrivacy & Private AIUnstoppable DeFiNEAR AI Cloud TEE
Step 1 — Compose the intent
Try a preset first — no key or wallet needed for this step. The evidence pack is built live from NEAR testnet RPC, and the numbers are computed on this page (the agents judge them; they never invent them).
Step 2 — Key
No API key? Get the free $10 NEAR AI credit key at the NEAR Builders dashboard → “Create an API key” — about 10 seconds. The key is pasted only into this page, is never stored, and is sent only to cloud-api.near.ai. Never paste it into any chat.
Step 3 — Convene the swarm
All four agents run in parallel on the same intent + evidence pack. A verdict counts only when its TEE proof verifies green in this browser — a gateway-only or unverifiable answer is scored as a failure, not an approval. One disclosed exception: if the Sentry's primary model is unreachable (rate limit / gateway down — no answer at all), the page retries that one role with an equally TEE-verified fallback model (Qwen3-VL-30B) and marks it in the record. A fallback never rescues a REJECT or a failed proof.
Decision record
Seal this record on NEAR testnet in the TETRAD gate contract at mahidboss.testnet — only hashes, verdicts and the locally redacted intent (a deterministic local scan plus the Warden's reported leak types decide the redaction). Gas only, paid in test NEAR. Sealing itself moves no funds; execution (Step 5 below) is wired only for the canonical wrap intent and only after the on-chain record is re-read as APPROVED.
Run the swarm first — sealing needs this run's decision record.
Step 5 — Execute the approved intent
Execution never trusts this page's memory: clicking Execute re-reads the decision from the gate contract and proceeds only if the on-chain record says APPROVED_4_OF_4. Wired for the canonical wrap intent (wrap.testnet · near_deposit) from the connected wallet; other targets stay record-only.
Execution unlocks after a 4/4 decision is sealed on-chain.
Verify a sealed decision
Anyone can audit the gate — no wallet, no key. Paste an intent hash and this page reads the recorded decision straight from the contract.
Honest limits. Testnet only. The swarm guards this page's verdict and execution path — it cannot stop a wallet used elsewhere. Agent verdicts are LLM judgements over the evidence pack, not formal verification. Models that failed the public gate test (gateway-only signatures — DeepSeek V3.2, Kimi K2.6/K3, GLM-5.3, the DeepSeek V4.1 alt route, Gemini 2.5 Flash, GPT-5 Mini) were dropped from the swarm and are disclosed here and in the README. This page verifies signatures against the provider's attestation report; full TDX quote verification runs in NEAR's Verification Center.