See your AI usage in 10 minutes
Route AI traffic through the Joopler egress proxy for a live, signed record of every interaction.
Point your AI traffic through Joopler and watch a live, signed record of every AI interaction appear on your dashboard. No agent to install, no certificate, nothing decrypted. You change one proxy setting and you are monitoring.
The prod fleet is live at proxy.joopler.com (observe mode, TLS).
What you need
- A Joopler workspace where you are signed in as an admin.
- One machine, agent runtime, or CI job that calls an AI provider (OpenAI, Anthropic, Google, and others), so you have traffic to see.
Step 1: Create a proxy token
- Go to AI usage in the left nav.
- Click Issue proxy token and give it a name, for example
Corp egress. - Copy the token that appears. It starts with
jpx_and is shown once. Store it like a password.
The token identifies your workspace and is scoped to usage reporting only. You can revoke it anytime from the same screen.
Step 2: Point your traffic at the proxy
Set your HTTPS proxy to the Joopler egress endpoint, with your token as the password and the person or system name as the username:
https_proxy=https://alice@yourco.com:jpx_YOUR_TOKEN@proxy.joopler.com
http_proxy=https://alice@yourco.com:jpx_YOUR_TOKEN@proxy.joopler.com- The username (
alice@yourco.com) is recorded as the acting user on each event. Use a real identifier so your reports attribute usage correctly. - On a single machine or runtime, set these as environment variables.
- To cover a fleet of laptops, push the same proxy setting through your MDM.
Observe mode vs terminate mode
- Observe (default, no CA). Records who reached which provider and when, and tunnels the encrypted bytes unread. No TLS interception, zero device setup.
- Terminate (your CA configured). Decrypts AI traffic to run the full inspection pipeline (model policy, DLP, prompt-injection detection, output inspection) and can block on policy. It uses your organization's existing MITM CA; without a CA the proxy stays in observe mode. Non-AI hosts are never decrypted.
Every inspected event becomes a signed, hash-chained, timestamped evidence record on your AI usage dashboard, next to your reverse-proxy, ingested, and tool-call events.