Solutions · Automated Operations

Automation that stays inside your limits

Bots and agents can act continuously without holding unbounded authority.

Automation may request — it cannot exceed what you allowed

The argument

Instead of — A hot key that is all-or-nothing

The signer is not the executor

Authorisation and submission are separate steps with separate permissions — whoever submits cannot decide what it says.

Instead of — Guardrails only in your own code

Give automation exactly the operations and targets it needs, and withdraw that access without redeploying.

Instead of — A submission stack that is its own product

Authorised submission of operations you already approved. Opt-in, revocable, and never involving us holding your keys.

Instead of — Agent tooling without an operating policy

Sensitive changes still follow the governed lifecycle. Automation works inside policy — it does not replace it.

This covers

Who is allowed to move funds?

Whoever you name, and only for the operations you name them for. Roles decide who may request, who must wait, who may approve, and who may execute — and the contract refuses an unauthorised call before it reaches your funds, rather than relying on an interface to prevent it.
Roles and approvals
Can someone bypass the rules through the interface?

No — the interface cannot override policy. The same on-chain rules apply whether the request comes from the Platform, from your own application through the Protocol, or from a script, because enforcement sits in the contract rather than in any of the things asking.
Pre-execution security
What stops a compromised integration from draining an account?

Each operation type is limited to a list of permitted targets, so a mistyped address or a compromised integration has nowhere to send funds. Automation can hold a role and still be bounded by the same policy as a person — a signing key is not an all-or-nothing grant.
Automated operations
Do we have to use your application?

No. The Platform runs these operations in the browser; the Protocol builds the same rules into systems you already run. They enforce identically because they enforce in the same place — the contract — so the choice is about where your team works, not about how much control you get.
Build on the Protocol

Protocol in your own systems, or Platform in the browser.

Alpha · Testnet · Personal workspace