Reference
Troubleshooting
No calls arrive
- Make sure the app made a model call through the
openaioranthropicPython package. - Check
import zexl.autoruns before the client is created. - Check
ZEXL_API_KEYis set in that process, with the part after the dot. - Print
zexl.status()in the app. It shows whether capture is on, which hooks are active, and how many records were sent or dropped. - Look for a warning on the
zexllogger. - Check the dashboard's environment switch: a development key's calls are not in Production. Try All.
A model shows $0
Zexl does not know its price. Set one in Settings > Model prices.
Calls are in the wrong environment
The key decides. Create a key for the right environment, or set ZEXL_ENV if the key shows any.
"ZEXL_API_KEY has no salt part"
Use the full key shown at creation, including the part after the dot. If it is lost, create a new key; it starts a new hash history.
Claude Code calls do not show
Open a new terminal after editing your shell profile, and check OTEL_LOGS_EXPORTER=otlp is set. The header takes the key without the part after the dot.
The MCP server says it is not connected
Run "connect Zexl" again with your agent, or set ZEXL_READ_KEY to a read key. A send key does not work for reading.
Does the SDK slow my app?
About 0.05 ms per call, and sending happens on a background thread. If Zexl is down, your app carries on and records are dropped.
How do I turn it off?
Set ZEXL_DISABLED=1, or remove the import.