Install

sphere.exe ships as a single Windows executable for 64-bit Windows 10 and 11.

Steps

1. Sign in to your account at sphere-exe.com and open the Dashboard.
2. Click Download client to grab the latest installer.
3. Run the installer. Windows SmartScreen may warn about an unsigned executable on first launch — click More info → Run anyway.
4. Open the EVE Online client first and log in to one or more characters.
5. Launch sphere.exe and paste the license key from the dashboard into the sign-in window.

Requirements

• Windows 10/11, 64-bit
• 8 GB RAM (16 GB recommended for multi-client)
• An active EVE Online subscription
• Internet access for the cloud-side decision fallback

Updating

When a new build is available, sphere.exe shows an in-app banner. Click Update and the client will download and restart itself. Your settings, ore selections, and dock targets are preserved.

First run

The first time you launch sphere.exe, it walks you through a short setup wizard. Have the EVE Online client open and logged in before you start.

1. Sign in

Paste the license key from your account dashboard. The client validates it against the server and registers the current machine as a device. Active device counts and revocation are managed at /account/devices.

2. Pick the EVE client(s)

sphere.exe lists every running EVE Online process. Select the characters you want to control. You can change this selection while the bot is running.

3. Pick mining targets

For each selected character, choose which ores to mine and which belt to work. Defaults are sensible — veld and concentrated veldspar in the nearest belt — so you can usually accept and move on.

4. Pick a dock target

Choose a station or citadel for unloading. The client picks the nearest station by default; override only if you want a specific dock.

5. Start

Click Start in the main window. The bot enters the standard loop:

undock → warp to belt → approach → lock → mine
→ full hold? → warp to dock → unload → resume

The diagnostics panel shows live parser state. The action log shows the sequence of decisions and inputs sent to the EVE client.

Configuration

sphere.exe stores per-character configuration in %APPDATA%\gods-eye\client-config.json. The desktop GUI is the canonical editor; the JSON file is documented here for operators who want to inspect or script profile changes.

The file is a JSON array. Each entry is validated as a ClientProfile. Unknown nested sections such as mining.*, defense.*, or drones.* are not read by the client.

Profile fields

• pid - EVE process id for the bound client, or null before detection.
• character_name - detected character name, or null if unavailable.
• role - currently miner.
• home_system_id and target_system_id - numeric EVE system ids.
• home_station_name, target_system_name, and target_station_name - optional display names used by the GUI and docking flow.
• belt_id - optional target belt id.
• selected_ore_types - array of ore names. Empty means any ore.
• ore_hold_threshold_pct - unload threshold as a percentage from 0 to 100; the default is 95.0.
• sanderling_path - optional path override for the reader integration.
• dry_run - true means the client will not send real input.

Example

[
  {
    "pid": 1234,
    "character_name": "Example Pilot",
    "role": "miner",
    "home_system_id": 30000142,
    "home_station_name": "Jita IV - Moon 4 - Caldari Navy Assembly Plant",
    "target_system_id": 30000142,
    "target_system_name": "Jita",
    "target_station_name": "Jita IV - Moon 4 - Caldari Navy Assembly Plant",
    "belt_id": null,
    "selected_ore_types": ["Veldspar", "Scordite"],
    "ore_hold_threshold_pct": 95.0,
    "sanderling_path": null,
    "dry_run": true
  }
]

If an entry fails validation, the client skips that entry and keeps loading the rest of the file.

Troubleshooting

sphere.exe cannot find the EVE client

• Confirm the EVE Online client is running and you have logged in to a character. The bot needs a character in space or in station — not the launcher screen.
• Run sphere.exe as Administrator. The memory reader needs the same privilege level as the EVE process.

License key rejected

• Copy the key from /account rather than typing it. The key uses an unambiguous alphabet but it is case-sensitive.
• Renewed licenses rotate the key. If you renewed today, fetch the new key from the dashboard and update the client.
• If you hit the device cap, revoke an unused device at /account/devices and try again.

Bot stops at unload

• Make sure your dock target is reachable from the belt. Citadels with access controls require your character to have appropriate roles.
• Check the diagnostics panel for parser_warning: hangar_window_missing. The bot will wait for the hangar window to open before unloading.

Cold-start delays

• The first read after launch takes 5–15 seconds while the memory map is built. Subsequent reads are sub-second.
• If reads time out repeatedly, restart the EVE client first, then sphere.exe.

Detection concerns

We won't make ban-risk guarantees. The architecture choices — read-only memory, no patching, humanized input, no kernel hooks — are documented on /how-it-works.

Licensing FAQ

What does each tier include?

| Tier | Concurrent client cap | Monthly price | |---|---|---| | Solo | 5 | 20 USDT | | Fleet | 10 | 35 USDT | | Unlimited | unlimited | 50 USDT |

All tiers include the full miner role, decision-engine fallback, and referral tracking. Tiers differ only in how many simultaneous EVE clients you can drive against the same license.

What counts as a "device"?

A device is a Windows machine that has logged in with the license key. The device record is created on first login and persists across reboots. Logging in twice from the same machine reuses the existing device entry.

Can I move my license between machines?

Yes — revoke the old device at /account/devices, then sign in on the new machine. Revocation frees the device slot for future logins. Existing JWTs already issued to that device may remain usable until they expire.

What happens when the license expires?

The desktop client refuses to start the loop. Existing JWTs continue to verify, so the action log and diagnostics remain readable, but no actions will be issued until you renew.

Do unused days roll over when I renew?

No. Each paid invoice extends the license to today + 30 days. Renewing early forfeits any unused time on the current period. The buy page warns you when more than 5 days remain so you don't lose them by accident.

Is the license key rotated when I renew?

Yes. Each paid invoice issues a new key. Update the desktop client with the new key after renewing. Existing active keys are not revoked automatically yet, so they may remain usable until expiry unless an admin revokes them.

How is offline use handled?

JWTs issued by /v1/auth/login are valid for 24 hours and cached locally. The client keeps running for the lifetime of the JWT even if the network is flaky. After 24 hours offline the client must reach the server to mint a fresh JWT.

General FAQ

Will I get banned?

We can't guarantee what CCP will or won't action against. sphere.exe is built to behave like a careful pilot — it reads game state from process memory rather than patching, and sends input through the same Windows input surface a human uses. The architecture trade-offs are documented on /how-it-works. Use at your own risk.

Can I run sphere.exe in a virtual machine?

Yes. Memory-reading works in VMware and VirtualBox. GPU acceleration for the EVE client is the only practical limitation. Hyper-V Enhanced Session Mode is not currently supported.

Does sphere.exe send anything to CCP?

No. The client reads from EVE's own process and uses Windows SendInput for actions. There is no traffic to CCP servers from sphere.exe itself; the EVE client handles its own network I/O.

Do you support combat / ratting / hauling?

Not at launch. The miner role is the v2.0 ship role. Orca and Rorqual support are on the roadmap.

Do you collect telemetry?

The desktop client uploads anonymized state hashes when the local rule engine cannot decide and asks the cloud for a fallback. No screenshots, chat logs, or character credentials leave your machine.

What payment methods do you accept?

USDT-TRC20 only at launch. Payments are non-refundable.

How do I cancel?

Don't renew — the license expires automatically 30 days after the most recent paid invoice. There is no recurring charge.

How do I contact support?

Email support@sphere-exe.com. We aim to respond within 48 hours.