VERSION HISTORY
Command-Line Interface
Fetches the article and compares it with Version 2.
▸Version 2October 13, 2026, 4:45 PM+20−7
Changes shown against Version 1.
irm https://cli.myfundedperpetuals.com/install.ps1 | iex
The installer places fperp.exe in %LOCALAPPDATA%\Programs\fperp and adds
that directory to your user PATH (new terminals pick it up automatically).
Only x64 Windows builds are published.
Verifying a download
Every release ships a SHA256SUMS file and an Ed25519 signature
(SHA256SUMS.sig) alongside its artifacts at
https://cli.myfundedperpetuals.com/vX.Y.Z/. The installers verify the
checksum of what they download, and fperp upgrade additionally verifies the
signature against a public key embedded in the binary, so a tampered release
is never installed.
Authenticate
− Create an API key in
− API Key Settings,
− then run:
bash theme={null}
fperp login
− The key is stored in your operating system's credential store (macOS
+ fperp login opens your browser to approve a new CLI session. After you
+ approve it, the CLI prints the session's expiry date and stores the
+ credential. The session expires on its own; run fperp login again to renew
+ it. Run fperp login status to see the current session.
+ On a remote or headless machine (for example over SSH), run
+ fperp login --manual. The CLI prints a sign-in link instead of waiting for
+ a browser on the same machine; open it anywhere, approve, and paste the code
+ the approval page shows.
+ To use a long-lived API key instead, create one in
+ API Key Settings
+ and run fperp login --with-api-key, which reads the key from stdin or a
+ prompt that does not echo it. fperp login --api-key also works, but
+ leaves the key in your shell history.
+ Credentials are stored in your operating system's credential store (macOS
Keychain, Windows Credential Manager, or the Linux Secret Service). Where no
− credential store is available, it falls back to a 0600 config file; see
+ credential store is available, they fall back to a 0600 config file; see
fperp login --help for the --store options. FPERP_API_KEY and
− --api-key override the stored key for one-off use.
+ --api-key on any other command override the stored credential for one-off
+ use.
+ fperp logout revokes a browser-approved session and removes the stored
+ credential.
Stay up to date
bash theme={null}
fperp upgrade
fperp upgrade downloads the latest release, verifies the signed checksums,
and replaces the binary in place. Use fperp upgrade --check to see whether a
newer version exists without installing it, and
fperp upgrade --version vX.Y.Z to install a specific release.
The CLI also checks for new releases in the background at most once per day
and prints a one-line notice on stderr when one exists. It never installs
anything on its own. To disable the check entirely, set
FPERP_NO_UPDATE_CHECK=1; the check is also skipped automatically when the
CI environment variable is set.
Uninstall
− Run fperp logout first so no API key stays behind in your OS credential
+ Run fperp logout first so no credential stays behind in your OS credential
store, then remove the binary (which fperp shows where it is) and delete the
~/.config/fperp directory.
SHA-256 262c1e5ed5b8970caead8fc52704fb2bf214f7ef1ebb386dbbffa116d415b8d5
▸Version 1October 11, 2026, 2:36 PM
First archived version.
Command-Line Interface
Source: https://docs.myfundedperpetuals.com/cli
Install the fperp CLI, authenticate, trade from your terminal, and keep the tool up to date.
What is fperp?
fperp is the official command-line client for the MyFundedPerps REST
API. Every API operation is available as a command with matching flags, so
anything you can do with curl against the API you can do with less typing:
bash theme={null}
fperp list-accounts
fperp get-market-quote "binance|BTCUSDT" --side buy --size 0.5
fperp create-order --data @order.json
Run fperp help for the full command list and fperp help for a
command's flags.
Install
macOS and Linux
bash theme={null}
curl -fsSL https://cli.myfundedperpetuals.com/install | sh
The installer detects your platform, downloads the latest release, verifies
its checksum, and installs to /usr/local/bin when that directory is
writable, otherwise to ~/.local/bin. It never asks for elevated privileges:
if the target directory is not writable it stops and tells you instead of
running sudo for you.
Optional environment variables, set before running the installer:
Variable | Effect
FPERP_VERSION | Install a specific release, for example v1.2.0
FPERP_INSTALL_DIR | Install into a different directory
Windows
In PowerShell:
powershell theme={null}
irm https://cli.myfundedperpetuals.com/install.ps1 | iex
The installer places fperp.exe in %LOCALAPPDATA%\Programs\fperp and adds
that directory to your user PATH (new terminals pick it up automatically).
Only x64 Windows builds are published.
Verifying a download
Every release ships a SHA256SUMS file and an Ed25519 signature
(SHA256SUMS.sig) alongside its artifacts at
https://cli.myfundedperpetuals.com/vX.Y.Z/. The installers verify the
checksum of what they download, and fperp upgrade additionally verifies the
signature against a public key embedded in the binary, so a tampered release
is never installed.
Authenticate
Create an API key in
API Key Settings,
then run:
bash theme={null}
fperp login
The key is stored in your operating system's credential store (macOS
Keychain, Windows Credential Manager, or the Linux Secret Service). Where no
credential store is available, it falls back to a 0600 config file; see
fperp login --help for the --store options. FPERP_API_KEY and
--api-key override the stored key for one-off use.
Stay up to date
bash theme={null}
fperp upgrade
fperp upgrade downloads the latest release, verifies the signed checksums,
and replaces the binary in place. Use fperp upgrade --check to see whether a
newer version exists without installing it, and
fperp upgrade --version vX.Y.Z to install a specific release.
The CLI also checks for new releases in the background at most once per day
and prints a one-line notice on stderr when one exists. It never installs
anything on its own. To disable the check entirely, set
FPERP_NO_UPDATE_CHECK=1; the check is also skipped automatically when the
CI environment variable is set.
Uninstall
Run fperp logout first so no API key stays behind in your OS credential
store, then remove the binary (which fperp shows where it is) and delete the
~/.config/fperp directory.
SHA-256 542aece80ea35e749fac4b69398df2908c5c8095f7aa07d5fb174d97b9c111b4