Understand the Auto Trader first. Then decide how automated you want to be.

fdv.lol’s Auto Trader is an engine: it watches Pumping Radar leaders, runs a chain of safety gates, quotes routes, executes, and manages exits. Agent Gary adds an agentic, approval-based decision layer for entries -the system does the measuring, but it won’t buy unless Gary explicitly approves.

Get 1:1 coaching How Auto Trader works Explore tools
No guarantees. This is experimental software. Trading is risky and you can lose money. Start small, use a burner wallet, and verify links.
Client-side
Open-source
Guardrails

How it works

Auto Trader is designed to avoid preventable failure modes first (bad routes, low liquidity, insufficient data), and optimize second. When Agent Gary is enabled, buys become approval-based -still inside the same hard safety gates.

  • 1

    RPC + preflight

    Use a CORS-capable Solana RPC endpoint. The bot starts with a preflight check; if RPC is unhealthy, it stops.

  • 2

    Two-wallet pattern

    Trade from a dedicated Auto Wallet (burner). Set a Recipient (your main wallet) for Return/unwind.

  • 3

    Choose your decision layer

    Manual mode is rule-driven. Agent Gary mode is approval-based for entries (requires your provider key).

  • 4

    Run it as a loop (not a one-off)

    The engine ticks repeatedly: evaluate candidates, manage positions, and apply exits. Agent Gary can veto entries and reduce churn.

Agentic advantage (practical)

Approval required: entries only happen when Gary returns an explicit “buy” decision.
Veto + reasons: skips come with a rationale so you can tune constraints without guessing.
Bounded tuning: Gary may suggest small, stable adjustments to allowed knobs; values are validated and clamped.
Learning loop: outcomes can be fed back so later decisions are grounded in your session history.

Trust anchors

  • ✓

    Open-source, verifiable links

    Start from the official repo and domain. Be suspicious of DMs and lookalike domains.

  • ✓

    We don’t hold your funds

    It runs client-side. You control keys and execution; the agent does not receive private keys.

Tools inside fdv.lol

Auto Trader is one workflow. fdv.lol also includes additional modules for monitoring, execution, and repeatable operations. Use what you need, keep constraints explicit, and keep balances small while you evaluate.

Auto Trader + Agent Gary

The automation loop: evaluate candidates, run safety gates, execute routes, and manage exits. Enable Agent Gary when you want approval-based entries and bounded tuning suggestions.

Other workflows

  • •

    Sentry

    Monitoring-first workflows that help you watch conditions and reduce surprises.

  • •

    Hold / Follow

    Repeatable position-management styles you can run with explicit constraints.

  • •

    Volume

    Operational tooling for controlled repetition -only use with strict limits and conservative budgets.

Verify in source Open the app

Recommendation: start by reading the guide, then do a short sanity run before expecting any performance.

Safety checklist (read this first)

This is intentionally conservative. A “clean” first session is one where you avoid avoidable mechanics.

  • !

    Use the two-wallet pattern

    Auto Wallet = dedicated trading wallet. Recipient = your main wallet for Return/unwind.

  • !

    Keep fee runway

    Fund enough SOL for buys and fees/rent. Many failures look like “bugs” but are fee starvation.

  • !

    Verify the domain + links

    Only trust fdv.lol and the official repo. Be cautious with DMs and lookalike domains.

  • !

    Expect skips (that's the system working)

    Common skip reasons are protective: no route/quote, insufficient samples, edge gates, or simulation enforcement.

  • !

    Verify your mode

    If Agent Gary is enabled but a key is missing, buys are blocked by design. Confirm “ACTIVE” before judging behavior.

Disclosure: fdv.lol is a research/education tool and is not financial advice. Trading is risky; you can lose money.

Get 1:1 coaching

Get hands-on help to set up your bots safely: RPC, wallets, safety posture, and how to confirm your mode.

What we'll cover

A short, practical 1:1 that matches how the system actually behaves. We'll set RPC, create/fund the Auto Wallet with fee runway, set a Recipient, and identify the key log lines that confirm a healthy session. If you enable Agent Gary, entries become approval-based: the bot measures and gates, and only enters on explicit approval.

Read the full Auto Trader guide
By submitting, you agree to be contacted about 1:1 coaching and occasional safety/product updates. Policy.

Prefer to self-serve?

Start from sources, then launch when you're ready. You can always request coaching later.

See the Github repo Launch fdv.lol Telegram support

Tip: verify links from the repo and use a burner Auto Wallet with a Recipient set.

FAQ

Short answers to the questions people ask before running automation.

Do you hold funds or run accounts for users?

No. It’s client-side tooling -you control keys and execution. Use explicit limits and small balances while testing.

What is Agent Gary, exactly?

An optional decision agent for Auto Trader. With Gary enabled, entries are approval-based: the bot won't buy unless Gary approves.

Does Agent Gary get my private keys?

No. He receives a compact, precomputed signals payload and returns a JSON decision. Keys stay with you; signing happens locally.

Why didn't it buy anything?

Often it's a gate, not a bug: no route/quote, insufficient leader series, edge/simulation enforcement, or Gary mode enabled without a key (buys blocked by design).