AI trading agents. Local execution. Your control.

Turn Trading Instructions into Agent Workflows

AI chat, crypto trading agents and local execution in one Windows workspace. Describe the task, review the plan and approve the operation.

FRB / OVERVIEW

Inside the execution workspace.

A visual map of the conversation, operation plan and local execution boundary.

FRB / OVERVIEWLocal signingAIInstructionA/BSelected contextFRBPlan!Approval1Wallets2Network3PermissionsFRB / EVM + SOLANA01
Illustrative workflow, not an application recording or a live transaction. No funds or network requests.
01 / 06

Intent enters the workspace

A plain-language instruction opens a reviewable workflow. Missing context stays visible.

Intent enters the workspace

A plain-language instruction opens a reviewable workflow. Missing context stays visible.

FRB / OVERVIEWLocal signingAIInstructionA/BSelected contextFRBPlan!Approval1Wallets2Network3PermissionsFRB / EVM + SOLANA01

Illustrative workflow, not an application recording or a live transaction. No funds or network requests.

Plan generation is not a signature. Provider acceptance is not confirmation. Review the actual result before retrying.

FRB / HOME

One instruction. Every handoff in view.

Follow a task from conversation to local signing and the submission lifecycle.

One instruction. Every handoff in view.
Illustrative workflow, not an application recording or a live transaction. No funds or network requests.

Static overview. Open the walkthrough to explore each stage.

  1. 01Describe the operation

    Start with your goal. The conversation captures the task, not your private keys.

  2. 02Build the plan

    Turn the instruction into ordered operations with explicit inputs and dependencies.

  3. 03Review the context

    Inspect the selected wallets, network, destinations and fee reserve together.

  4. 04Approve the exact operation

    The approval boundary separates a proposed plan from permission to sign.

  5. 05Sign on your device

    Signing remains on Windows. The selected provider receives the prepared submission, not your keys.

  6. 06Check submission

    Inspect the provider response. Accepting the submission does not establish inclusion or execution.

  7. 07Check inclusion

    Check whether the operation was included. An inclusion result still needs the relevant confirmation checks.

  8. 08Check confirmation

    Review the actual confirmation state and each operation outcome before preparing another action or retry.

Talk in goals. Work in clear steps.

Describe your task in natural language. Keep the network, wallet context, parameters and approval steps visible in the resulting plan.

One conversation. More than one wallet.

Bring transfers, token tasks, liquidity operations and private bundle preparation into a shared workflow instead of switching between disconnected tools.

From a plan to an accountable operation.

Separate preparation, simulation, signing, submission and confirmation. Understand what has happened, what needs your approval and which result still needs checking.

Build an agent around your rules.

Define the task

Give the agent a specific goal and the wallet and network context it needs. Resolve missing inputs before moving on.

Set the boundaries

Keep amounts, destinations, permissions and execution limits explicit. Review the proposed actions instead of granting an open-ended mandate.

Review the handoff

Inspect preparation and simulation separately from approval, local signing and submission. Check each returned outcome.

EVM and Solana. The right execution context.

EVM workflows

Review chain ID, wallet permissions, nonce, gas and the configured RPC or private-submission provider. Flashbots routes depend on chain and provider support.

Solana workflows

Review accounts, token programs, blockhash validity, fees and the selected RPC or Jito route. Bundle acceptance, inclusion and confirmation are different states.

Control stays visible.

Local transaction signing and AI inference are different boundaries. Review the AI provider and what context it receives. Keep private keys, seed phrases and provider credentials out of chat. Protect your Windows device and verify every operation before approval.

Control stays visible.

Before you build your workflow

Is FRB a custodial exchange or a wallet?

FRB is a non-custodial execution workspace for your wallets. It organizes network context, operations and approvals while transaction signing stays on your Windows device. You control the wallets and provider connections; FRB is not a hosted account holding your balance.

How is FRB different from a chatbot?

FRB connects AI chat to structured trading workflows: wallet and network context, a reviewable operation plan, approval and local execution. A chat response alone is not an executed trade.

Does an agent mean unlimited automatic trading?

No. Define the task and its boundaries, review the proposed actions and retain approval over signing. Do not treat an agent as an unrestricted mandate.

Does all AI run locally?

Local signing does not imply local AI inference. Review your chosen AI provider and the context sent to it. Never put private keys or seed phrases into a prompt.

Does AI guarantee profit or bundle inclusion?

No. Market prices, liquidity, fees, ordering and provider conditions still affect the outcome. Simulation, AI output and submission acceptance do not guarantee execution or returns.

Can I run the agent on my phone?

FRB Agent runs on Windows. You can read these guides on mobile and copy the download link for your Windows computer. Use the matching EVM or Solana dashboard to connect the installed agent.

From a conversation to a plan you can review, approve and run.

Build Your Workflow