Introduction to Mandate
What Mandate is, why autonomous agents need controlled financial authority, and core architecture.
What is Mandate?
Mandate is an autonomous spending firewall and policy-enforced custody layer for artificial intelligence agents on the NEAR Protocol. It empowers users and treasury operators to delegate real tasks and budgets to autonomous multi-agent swarms without ever handing over master private keys or granting unconstrained financial authority.
In traditional automation, granting an agent an API key or a wallet seed phrase gives it complete, binary access to all stored assets. Mandate replaces this dangerous model with deterministic financial policy enforcement executed within hardware-isolated Trusted Execution Environments (Intel SGX TEE) powered by OutLayer.
The Problem Mandate Solves
Large Language Models (LLMs) and autonomous agents are probabilistic reasoning engines. While they excel at planning, researching, writing code, and orchestrating workflows, their probabilistic nature makes them fundamentally unreliable for financial custody:
- Hallucinations & Parameter Errors: An agent could mistakenly submit 100 NEAR instead of 1 NEAR, or send funds to an unintended address.
- Prompt Injection Attacks: Malicious third-party data or compromised tool responses can instruct an agent to drain its connected wallet.
- Recursive Tool Loops: Unchecked agent loops can rapidly deplete working balances in minutes through runaway API calls or repeated transactions.
- All-or-Nothing Custody: Developers previously had to choose between requiring human approval for every trivial micro-payment or granting full, unrestricted wallet access.
Core Architectural Principle
The Four Central Responsibilities
Decompose high-level natural language goals into directed acyclic graphs (DAGs), execute research tools, and propose financial operations with explicit parameters.
Evaluates every proposal against deterministic constraints: maximum budget, per-tx limit, human approval thresholds, expiration dates, and recipient allowlists.
Defines financial bounds, approves execution plans, funds dedicated custody accounts, reviews high-value requests, and retains emergency revocation power.
Holds agent signing keys in hardware-isolated enclaves. Signs NEAR transactions only after receiving cryptographically nonced authorization envelopes from Mandate.
How Mandate Differs from Other Systems
| Capability | Ordinary AI Assistants | Traditional Automation | Mandate Platform |
|---|---|---|---|
| Financial Authority | None (Advisory only) | All-or-Nothing API keys | Fine-grained Mandate Policy |
| Key Custody | N/A | Environment variables on host | OutLayer Intel SGX TEE |
| Human-in-the-Loop | Manual copy-paste | Rarely supported | Automatic Threshold Escrow |
| Onchain Settlement | None | Centralized payment rails | Native NEAR Protocol |
| Execution Evidence | Chat text | Log files | SHA-256 Hash Chained Audit |
Architecture Overview
The diagram below visualizes how requests travel from user authorization to autonomous agent proposing, through the Universal Policy Engine and Execution Boundary, to OutLayer TEE and the NEAR Testnet blockchain:
Protected enclaves holding agent private keys. Signs NEAR transfers only when valid execution envelope is verified.
Final settlement blockchain. Transactions broadcast and independently confirmed via RPC node state proofs.
PostgreSQL 18.6 durable checkpoints, SHA-256 hash chaining, idempotency keys, and multi-round lease recovery.