Agent wallets — total
What people run on OutLayer
Every example opens ready to run — no project, key or code required.
Built on OutLayer
All products →Live products running their critical path on OutLayer compute and custody.
NEAR EmailSecure, wallet-based encrypted email for the NEAR ecosystem.
TEE-Secured Price OracleOn-demand oracle with sustainable economics for NEAR Protocol.
NEAR FMAI music generation & social marketplace powered by OutLayer agents.If you run an AI agent
A protected wallet for an agent that runs elsewhere — Railway, a server, Claude Code on your machine.
- The keys stay in a hardware enclave; the agent holds an API key
- A leaked key pays only the addresses you approved, within your limits, and withdraws only to you
- Paid from any chain, pays on any chain; every signature is in an audit log
Or let the agent set itself up with this skill:
If you build
One platform, many entry points — pick the one your stack speaks.
If you sign off on risk
Trust is verified, not promised — check every layer yourself.
- Intel TDX enclaves, DCAP-verified against Intel PCS
- Enclave measurements approved on-chain by a DAO
- Keys derived via NEAR MPC — leave with your vault anytime
- Re-check any execution offline with OutLayer Verify
- Open source, with a public attestation portal for the fleet
Proof that does not depend on us
Written for the security review. Every claim below is checkable without trusting our servers, our website or our word.
Every worker runs in an Intel TDX enclave. Its attestation quote chains to Intel's root certificate — not to any key we hold. A forged quote fails the chain, whatever our infrastructure claims.
Enclave measurements are approved on NEAR by a DAO. A worker whose build is not on the on-chain list cannot take jobs, and you can read that list from any RPC node.
Each execution returns an enclave-signed attestation binding the code hash, input hash and output hash — what ran, on what, producing what. Receipts for on-chain calls live in the NEAR transaction itself.
OutLayer Verify is an open-source binary your engineers run on their own machines: no account, no API key, Intel's root compiled in, payloads read back from NEAR. Bring your own collateral and the verdict does not touch our servers at all.