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 Bolt

Use APXY to debug the API calls Bolt-generated apps make in production

Bolt builds apps fast. APXY lets you inspect the HTTP traffic those apps produce — so when an API integration fails, you see the exact request and response instead of guessing from the generated code.

Recommended workflow

Point your Bolt-generated app through APXY's local proxy to capture real API traffic and debug integration failures with evidence.

Install APXY and start the proxy on your local machine or development environment.
Configure your Bolt-generated app to route outbound requests through APXY's proxy address.
Trigger the failing API call or third-party integration inside the app.
Inspect the captured request and response in APXY, mock the endpoint if needed, and replay after any fix.

Why APXY fits

Bolt-generated code can be hard to trace — APXY shows you exactly what the app is sending and receiving.
Mocking unstable third-party APIs lets you keep iterating without waiting for upstream fixes.
The replay feature lets you verify that a code change actually fixed the API response without redeploying.

Take the fast path

Install Free View Examples

FAQ

What is APXY for Bolt?

How do you use APXY with Bolt?

Install APXY and start the proxy on your local machine or development environment. Configure your Bolt-generated app to route outbound requests through APXY's proxy address. Trigger the failing API call or third-party integration inside the app. Inspect the captured request and response in APXY, mock the endpoint if needed, and replay after any fix.

Why do developers pair APXY with Bolt?

Bolt-generated code can be hard to trace — APXY shows you exactly what the app is sending and receiving. Mocking unstable third-party APIs lets you keep iterating without waiting for upstream fixes. The replay feature lets you verify that a code change actually fixed the API response without redeploying.