Trade with AI agents.
Keep control of your keys.

Agentic trading lets software move from market signal to trade action. Lore gives agents useful authority without handing them custody.

Trade Hyperliquid through Plan, Auto, or Bypass policy modes. Lore separates intelligence from signing, so a 2-of-2 MPC wallet keeps the private-key boundary under your control.

Non-custodial by design · Policy checked before signing · Revocable any time

lore · agent
PlanAutoBypass

agent proposes

policy check

daily cap $5k

market allowed

max leverage 5×

Signedauto-signed in policy

tx 0x42eb…b738a · 1-round TSS-MPC · no key recombination

threshold 2-of-2 · you + agentaudit-logged
WHAT IS AGENTIC TRADING?AGENTS PROPOSEPOLICY DECIDESMPC SIGNSPRIVATE KEYS STAY YOURS

Agentic trading · defined

Software that can move from market signal to trade action.

An agentic trading system does more than surface a chart or send an alert. It can interpret context, choose an action, and carry that action toward execution. That makes the signing boundary—not just the model—the critical piece of the system.

01

Observe

The agent reads market data, positions, and the strategy context you allow it to see.

02

Decide

It turns a signal into a concrete trade proposal: market, size, leverage, and execution instructions.

03

Act under policy

The wallet checks that proposal against your limits before anything is signed or sent on-chain.

The private-key boundary

A trading agent needs permission to act. It does not need your key.

Giving model infrastructure a full private key turns every prompt injection, provider compromise, and bad decision into a custody event. Lore makes the agent one participant in a policy-controlled signing system instead.

Fragile boundaryKEY EXPOSED

Agent holds the signing secret

  • One compromised runtime can become full wallet control.
  • Strategy permission and custody collapse into the same credential.
  • Stopping the agent may depend on rotating or moving the wallet.
Lore boundaryPOLICY GATED

Agent participates in MPC signing

  • No provider-side key recombination and no plaintext key handed to a model.
  • Markets, leverage, notional, and loss limits are checked before signing.
  • You can change policy, return to proposal-only mode, or revoke authority.

System architecture

Five layers between a signal and a signed trade.

From market feed to on-chain execution, every Lore trade passes through one policy engine — the layer you own, tune, and can revoke. Nothing signs until it clears the rules you set.

LORE · SYSTEM ARCHITECTUREFIG.01 · EXPLODED VIEW
Exploded-view diagram of the Lore trading agent stack: market feed, signal model, policy engine, MPC signer, and on-chain execution layers, connected by leader-line callouts.

The policy engine

One policy engine. Three levels of trust.

An agentic wallet is just a policy engine between a proposer and an execution authority. Lore gives you the exact hierarchy that LLM coding harnesses converged on — set it per wallet, change it any time.

01

Plan

Propose only

Every trade waits for your signature. The agent reads the market, drafts the order, and parks it in the proposal pool. Nothing executes without you.

02

Auto

Policy-gated autonomy

In-policy trades sign themselves. Anything outside your caps, markets, or leverage limits degrades gracefully to a proposal instead of failing.

03

Bypass

Delegated window

Hand the agent a time- and value-capped window. It signs anything it can construct inside the window — full throughput when you want it, bounded by design.

The custody spectrum

“Non-custodial” is a spectrum. Lore sits at the edge.

Most agent wallets rebuild your key inside an enclave they operate. Lore is the rightmost multi-admin MPC architecture shipping at consumer scale — no provider ever reconstructs your key.

◄ More custodialYou in control ►

Coinbase / Kraken

Provider holds the keys

Fireblocks

Provider nodes co-sign

Privy / Turnkey

Key rebuilt in provider enclave

Lore

No provider-side key recombination

Bare EOA + Ledger

No provider in the loop

Frequently asked questions

No. Lore is built on threshold MPC with no provider-side key recombination. Your signing share never leaves your device, and Lore stores ciphertext — never plaintext keys.

Give an agent authority—not your private keys.

Request access to Lore. Connect a Hyperliquid strategy, set the boundaries, and move from supervised proposals to policy-gated execution when you are ready.