APXY is a local network proxy and debugging tool that captures, inspects, mocks, replays, and diffs HTTP/HTTPS traffic. It is built for developers and AI coding agents with a CLI-first workflow and an optional Web UI.

How is APXY different from Charles Proxy or mitmproxy?

APXY is purpose-built for the modern developer workflow including AI coding agents. It provides structured output (TOON format) that AI agents can reason over, a CLI-first API for scripting and automation, and first-class support for CI/CD, Docker, and headless environments. Unlike Charles Proxy, APXY requires no GUI and unlike mitmproxy, it includes API mocking with scripting and a built-in Web UI.

Does APXY work with AI coding agents like Claude Code and Cursor?

Yes. APXY has dedicated integrations for Claude Code, Cursor, GitHub Copilot, and OpenAI Codex. It returns compact, structured network traffic so AI coding agents can reason over real HTTP requests and responses instead of screenshots or raw HAR files.

APXY has a free tier that lets you capture traffic and explore the Web UI with no account or credit card required. Paid one-time licenses (Pro at $59, Personal at $79) unlock unlimited traffic history, API diagnosis, scripting, breakpoints, network simulation, and multi-device access.

Does APXY work in CI/CD pipelines and Docker?

Yes. APXY runs headlessly and works in local development, CI pipelines, SSH sessions, Docker containers, and background scripts. The core CLI workflow stays the same across all environments.

What operating systems does APXY support?

APXY supports macOS, Linux, and Windows.

For Aider

Use APXY with Aider to give your terminal AI agent real network evidence

Aider edits your code from the terminal. APXY captures the HTTP traffic your code produces so Aider can debug failures with real request and response data instead of guesswork.

Recommended workflow

Start APXY before running your app, then share captured traffic with Aider so it can diagnose the exact failing request.

Run APXY in the background to intercept your app's HTTP and HTTPS traffic.
Reproduce the API failure or webhook error you want Aider to investigate.
Export the failing request from APXY as a cURL command or JSON and paste it into your Aider session.
Ask Aider to find the root cause, patch the code, then replay the request in APXY to verify the fix.

Why APXY fits

Aider works best with precise, structured evidence — APXY's export formats give it exactly that.
The replay loop lets you verify a fix without re-running the full app each time.
Keeping APXY running headlessly alongside Aider fits naturally into a terminal-first workflow.

Take the fast path

Install Free View Examples

FAQ

What is APXY for Aider?

Aider edits your code from the terminal. APXY captures the HTTP traffic your code produces so Aider can debug failures with real request and response data instead of guesswork.

How do you use APXY with Aider?

Run APXY in the background to intercept your app's HTTP and HTTPS traffic. Reproduce the API failure or webhook error you want Aider to investigate. Export the failing request from APXY as a cURL command or JSON and paste it into your Aider session. Ask Aider to find the root cause, patch the code, then replay the request in APXY to verify the fix.

Why do developers pair APXY with Aider?

Aider works best with precise, structured evidence — APXY's export formats give it exactly that. The replay loop lets you verify a fix without re-running the full app each time. Keeping APXY running headlessly alongside Aider fits naturally into a terminal-first workflow.