Cursor for agentic trading · policy-controlled MPC available now

Control for agentic trading.

Lore separates model output from signing authority. Plan, Auto, and Bypass govern what can reach capital through policy-controlled, non-custodial MPC signing.

Get accessSee what’s supported

Hyperliquid first · Start in Plan · Multi-agent orchestration is roadmap direction

Roadmap illustration · not a shipped runtimeHYPE-PERP · LONG · $2,400 · 3×

Roadmap agent layer

01

Observer

market + account state

ready
02

Strategist

trade intent

complete
03

Risk

size + exposure review

pass

Policy

signed mandate
MarketHYPE-PERP PASS
Notional$2,400 / $5k PASS
Leverage3× / 5× PASS

2-of-2 MPC path

Policy clears before signing

Execution

Eligible

The action can reach the authorized signer. Intelligence and authority remain separate.

Authorized
Hyperliquidillustrative

Product state

Shipped controls. Clear roadmap.

Lore’s non-custodial MPC and approval controls are the supported foundation. The broader orchestration system is the direction being built on top.

Supported now

Available foundation
Model output stays separate from signing authority.
Plan, Auto, and Bypass define distinct approval semantics.
Policy evaluation clears before the normal MPC signing path.
An agent can participate without receiving an unrestricted private key.
Operators can narrow, return to Plan, or revoke subsequent authority.

Roadmap direction

Not a shipped claim
Multi-agent workflows across strategy, risk, execution, and monitoring.
Role-specific permissions for specialized agents and services.
Explicit handoffs between agent and service responsibilities.
Complete execution traces from intent through venue reconciliation.
Automatic halt conditions with reviewed restart decisions.

Roadmap: one strategy, coordinated execution.

Lore’s roadmap extends the supported policy and MPC foundation into a multi-agent sequence of responsibilities, permissions, handoffs, execution traces, and reviewed halt or restart decisions.

01

Observe

Market, funding, positions, venue and data health.

02

Form intent

Turn a thesis or model output into a structured action.

03

Review risk

Challenge size, leverage, exposure and invalidation.

04

Check policy

Resolve the action against the signed mandate.

05

Authorize

Route eligible execution to the permitted signing path.

06

Reconcile

Match the venue result back to the action and its state.

Direction: multiple agents contribute through distinct, role-specific authority.

Choose how each action earns approval.

Plan, Auto, and Bypass change the approval path. They do not turn model confidence into signing authority.

01

Plan

Prepare the action. You approve execution.

Approval

Per action

Outside authority

Remains a proposal

02

Auto

Eligible actions reach the authorized signing path.

Approval

Signed policy

Outside authority

Escalates for approval

03

Bypass

Broader delegated authority inside explicit hard bounds.

Approval

Scoped window

Outside authority

Blocked outside scope

Autonomy is a permission state.

Not a model setting

Keep model output separate from signing authority.

Lore checks a proposed action against policy before the normal MPC signing path. Agents can participate without receiving a standalone unrestricted private key.

Read the wallet architecture

Separate shares

Lore’s normal 2-of-2 path keeps the user and agent signing shares separate. No provider-held plaintext key is reconstructed.

Forward control

Narrow the mandate, move an agent back to Plan, or disable subsequent signing authority. Accepted venue orders are not reversed.

Policy boundary

Before signing

Approved markets and venuesconfigurable
Position and leverage limitsconfigurable
Daily notional and loss boundsconfigurable
Approval and escalation conditionsconfigurable
Authority expiry and revocationconfigurable

Bring the intelligence. Keep authority governed.

Today, Lore keeps model judgment separate from policy-controlled execution. Connecting specialized, role-specific agents into one coordinated runtime is roadmap direction.

01operator input

Your strategy

Bring your thesis, rules, signals, and custom agents.

02near-term direction

Persistent agents

Connect role-specific runtimes as orchestration support becomes available.

03research layer

rSwarm research

Use tuned market models and backtesting as a research source, separate from execution authority.

External-agent connections, role permissions, and agent-to-agent handoffs are product direction, not shipped integration claims.

Product-state explicit

The orchestration layer starts with shipped wallet infrastructure.

Lore’s near-term orchestration direction builds on previous generations of non-custodial wallet and policy infrastructure.

$250K

Optimism RetroPGF

$50M

Peak AUM · Portfolio Token Protocol

3

Wallet architecture generations

Govern agentic execution without giving up control.

Bring a Hyperliquid strategy. Start in Plan, define the execution policy, and promote only proven actions to policy-gated Auto.