Cursor integration
Cursor request logs review
Cursor workflows can grow expensive when requests loop or context gets large. Logs are how you see what the client actually spent. NexRelay keeps the first test small and reversible.
Cursor request logsCursor API keyCursor prepaid APICursor gateway
Why this setup works
A dedicated Cursor key keeps testing separate from production while NexRelay adds prepaid balance checks and request logs.
Recommended setup
Run one request, then review the log row for model, token meters, status, and billed amount.
- One key per Cursor workflow
- Start with a small budget
- Keep the model list narrow
- Review the first log entry
What to verify
Make sure the logged request matches the client and model you expected.
FAQ
Why do request logs matter?
They explain where credits went and make support much easier.
What should the log show?
At minimum, model, token meters, status, and billed amount.