Security & trust

Autonomy without
unbounded authority.

M2M separates account ownership from routine agent execution so software can transact under explicit controls rather than possessing unrestricted wallet power.

OWNER / PASSKEYSMART ACCOUNTPOLICYDELEGATED AGENTMARKETPLACE
CONTROL 01

Passkey-controlled ownership

The account owner retains the high-trust authority used for sensitive account and recovery actions.

CONTROL 02

Delegated Agent signer

Routine machine execution can use restricted delegated authority instead of exposing owner credentials.

CONTROL 03

Spending policies

Per-request and delegated spending constraints limit what an autonomous workflow may purchase.

CONTROL 04

Restricted execution

Delegation is designed around permitted M2M actions rather than unrestricted wallet control.

CONTROL 05

Revocation & recovery

Delegated authority can be revoked and re-established without handing permanent ownership to an agent.

CONTROL 06

On-chain accountability

Production settlement is anchored on Base Mainnet for externally verifiable transaction evidence.

Policy enforcement

What happens when an agent exceeds policy?

The transaction should be rejected rather than silently bypassing the delegated spending boundary. See the documentation for the operating model.

Read the docs