Compare

Akev vs HTTP Toolkit

Akev and HTTP Toolkit compared on price, free features, scripting, HTTP/3, MCP and headless use, and how to import your HTTP Toolkit rules.

Details of other products as checked in November 2026; check their websites for current ones. Akev is not affiliated with them, and their names are their owners’ trademarks.

HTTP Toolkit is an open-source HTTP(S) debugging proxy with an Electron desktop app, a free tier and a Pro subscription. Akev is an open-source HTTP(S) debugging proxy with a Rust core and a Tauri desktop app: free, with an optional Pro licence you pay for once. Both are licensed under the AGPL, and Akev imports HTTP Toolkit's rule exports. The HTTP Toolkit details below are for version 1.27.4; see httptoolkit.com for current prices and features.

At a glance

Akev HTTP Toolkit
Price Free. Pro: $49 once, with 1 year of updates; $25 for each further year, optional Free tier. Pro: €8/month or €72/year before VAT, subscription only
Account None. Pro keys are checked offline Needed for Pro
Open source Yes, AGPL-3.0-or-later Yes, AGPL-3.0
Platforms macOS, Windows and Linux; command-line tool; Docker image macOS, Windows and Linux
Desktop app Tauri, using the system's webview. The UI is built into the app Electron. The UI loads from app.httptoolkit.tech and is cached
Mock and rewrite rules Free Pro
Breakpoints Free Free
HAR import and export Free Pro
Resend a captured request Free Pro (the Send page is free)
Upstream proxies, client certificates, TLS passthrough Free Pro
Scripting JavaScript script rules (Pro) No
System proxy Yes No, by design
Transparent capture Linux only (Pro) No
HTTP/3 Opt-in, with limits No
Protobuf and gRPC Decoded without a schema (free); .proto files and descriptor sets (Pro) Decoded without a schema
MCP for AI agents Built in. Read tools free and unlimited; tools that change things are Pro Built in. Some reads capped per session on the free tier; rules and interceptor activation are Pro
Headless use akev start, akev capture for CI, Docker image No headless mode: traffic lives in the app window
Keeping traffic Saved sessions and autosave (free) In memory; export as HAR (Pro)
Mobile Android over ADB (a system CA on rooted devices and emulators), iOS by Wi-Fi proxy and profile, the iOS Simulator; WireGuard mode for any device (Pro) Android over ADB with its VPN app and system CA injection; Frida-based unpinning for Android and iOS
Maturity New: first release 0.1.0 Version 1.27.4

Where HTTP Toolkit is the better choice

  • Maturity. HTTP Toolkit has been in use for years, and its issue tracker goes back to 2018. Akev's first release is 0.1.0 and hasn't yet met as many devices, apps and networks.
  • Android and pinned apps. HTTP Toolkit sets up Android devices over ADB with its own VPN app and can inject its CA into the system store. Its Frida integration bypasses certificate pinning on Android and on jailbroken iOS devices. On an unrooted phone, Akev copies its CA to the device for you to install as a user CA, which apps must opt in to trusting. On rooted devices and emulators it also trusts it as a system CA until reboot, so far tested with emulators only. It has no pinning bypass.
  • API documentation. HTTP Toolkit Pro shows documentation for 2,600+ public APIs next to their traffic and validates requests against their OpenAPI specs. Akev has nothing like it.
  • WebRTC. HTTP Toolkit captures WebRTC and has rules for it. Akev doesn't handle WebRTC.
  • A library for tests. HTTP Toolkit's engine, Mockttp, can be used on its own in your test suite.

Where Akev is different

Price and licence

  • More is free. Mock and rewrite rules, HAR import and export, resending captured requests, copying requests as code, upstream proxies, client certificates and TLS passthrough are all in Akev Free. In HTTP Toolkit they need Pro.
  • Pro is paid once. $49, with a year of updates. Every version released during that year keeps Pro for good; another year of updates is $25 whenever you want it. There's no account, and the key is checked on your machine. See licensing.
  • Nothing is reset when a licence ends. When an HTTP Toolkit subscription lapses, the app resets its paid settings and stops keeping Pro-only rules. Without an Akev licence, Pro features pause, and rules and settings stay saved (without a licence).

Capture

  • System proxy. HTTP Toolkit leaves the system proxy alone by design. Akev can set it on Linux (GNOME, KDE), macOS and Windows, and restores your previous settings when it quits, even after a crash (system proxy).
  • Transparent capture (Pro, Linux only). Captures programs that ignore proxy settings, per app, per user or machine-wide. Akev writes the firewall commands for you to run as root (transparent capture).
  • WireGuard mode (Pro). Scan a QR code with the official WireGuard app and a phone's TCP traffic goes through Akev. QUIC is dropped so apps fall back to TCP, and the mode hasn't been tested with a physical phone yet: so far it has been checked end to end with a software WireGuard client (WireGuard mode).

HTTP/3, with limits

HTTP Toolkit doesn't proxy HTTP/3. Akev can use HTTP/3 to servers, and can accept HTTP/3 from clients that send it to Akev directly. Both are off by default. Browsers that use Akev as their proxy still talk HTTP/1.1 or HTTP/2 to it, so for them HTTP/3 only applies on the upstream side (HTTP/3).

Tools

  • Scripting (Pro). onRequest and onResponse hooks in sandboxed JavaScript (scripting). Scripting is HTTP Toolkit's issue #37, open since 2019.
  • Compare two exchanges side by side, bodies and timing included (compare). HTTP Toolkit has no diff (issue #246).
  • WebSocket breakpoints. Pause, edit or drop individual messages (WebSockets).
  • Throttling. Limit bandwidth and add latency with a rule. HTTP Toolkit offers delays and timeouts.
  • Protobuf schemas (Pro). Import .proto files or descriptor sets and gRPC bodies show real field names (protobuf). HTTP Toolkit decodes without a schema only.
  • TLS fingerprint impersonation (Pro). Present a browser's TLS and HTTP/2 fingerprint to servers that block proxies (TLS fingerprints).

Automation

  • Headless. akev is one binary with the web UI built in. akev capture records a CI run to a HAR file, and there's a Docker image (CLI). HTTP Toolkit's command-line control and MCP server read traffic from the app window, so one has to be open.
  • MCP. Akev's read tools are free with no call limits, and akev mcp starts a headless Akev when none is running. Tools that send requests, change rules or launch clients need Pro (MCP).
  • Sessions. Save traffic under a name, reopen it later, or turn on autosave so it survives restarts (sessions).

Switching

Rules

Export your rules from HTTP Toolkit (exporting needs its Pro plan, so do it while your subscription is active). In Akev, open Rules → Import rules… and pick the .htkrules file, as a new group or replacing your rules (import & export). From the command line, akev start --rules mocks.htkrules or akev rules set mocks.htkrules does the same.

How the rules come across:

  • HTTP Toolkit rules don't stack; Akev's do. Each HTTP Toolkit rule becomes one Akev rule that handles the request, with rules for its delays and breakpoints in front of it where needed, so it behaves as before. Rule priorities are kept.
  • Rules Akev can't reproduce, such as callback matchers, WebRTC rules and webhook steps, come in disabled, with a note saying why.
  • A few transforms (match and replace on the host, path or query, replacing all headers) and JSON-RPC responses become generated script rules. Script rules need Pro to run; without it they stay saved but inactive.
  • HTTP Toolkit's built-in default rules come in disabled. Akev passes unmatched traffic through and serves its own CA.

Traffic

Export a HAR file from HTTP Toolkit (also a Pro feature there) and use Import HAR… in Akev's Traffic toolbar. Akev reads HTTP Toolkit's HAR files.

Clients and certificates

Akev's Connect page covers what HTTP Toolkit's interceptors do: Chromium browsers and Firefox with their own profiles, fresh and existing terminals, Android over ADB, Docker, Electron apps and, with Pro, running JVMs (connect clients). Devices that trust HTTP Toolkit's CA have to trust Akev's too (certificates).

See pricing for what Free and Pro include, or download Akev.

Type to search guides, the CLI and the API.