All agents must be registered and approved through the Synclear agent registry before they are permitted to submit any protocol interactions. Unregistered agent addresses will be rejected at the contract level regardless of instruction source.
How It Works
Agent integration in Synclear is built on three interlocking systems. A mandate defines what an agent is authorized to do and under what constraints. A spending limit engine enforces per-transaction, daily, and lifetime volume caps on-chain before any execution is allowed to proceed. An accountability layer records every agent action immutably, feeds a continuously updated trust score, and exposes a structured audit trail for compliance and reconciliation purposes. Together, these systems allow principals — protocol participants who register and authorize agents — to delegate operational work with precision. An agent can be authorized to deposit and withdraw USDC up to $50,000 per day, for example, while being explicitly prohibited from borrowing or accessing other asset classes. Mandate parameters are enforced by theMandateRegistry smart contract; no off-chain configuration can override them.
Key Features
Mandates & Limits
Define and manage on-chain authorization records that govern what actions an agent may take, which protocols it may access, and how much volume it may move.
Accountability
Every agent action is recorded on-chain. Agents accumulate a trust score over time, and a full audit trail is available for compliance reporting and reconciliation.
Supported Agent Types
Synclear’s mandate system is agent-framework agnostic. Any autonomous program that can sign transactions with a registered agent address can operate under a mandate. Common integration patterns include:- Treasury management agents that rebalance stablecoin positions across lending pools
- Yield optimization bots that move liquidity in response to rate changes
- Risk management agents that automatically deleverage positions when collateral ratios approach thresholds
- Automated repayment schedulers that service loan obligations on a defined cadence
Agent Registration Overview
Before a mandate can be created, the agent’s address must be registered against a principal account. Registration records the agent’s public key, an optional metadata URI, and the registering principal’s on-chain identity. Registration is a prerequisite for all mandate creation and does not by itself grant any operational permissions.Configure a Mandate
Step-by-step instructions for defining mandate parameters, selecting permitted actions, and activating an agent authorization on-chain.
Understand Trust Scoring
Learn how agents build a trust score over time and how higher scores unlock expanded spending limits and protocol access.