|Ben @ Grepture

Route Cursor Through Grepture — Observability, Cost Tracking, and PII Protection for Your Team

You can now route all Cursor AI traffic through Grepture. See every request, track token costs per developer, and protect sensitive data — with a 2-minute setup.

Cursor is powerful. It's also a black box.

Cursor is one of the best AI-powered code editors out there. It autocompletes, refactors, explains code, and generates entire files — all powered by OpenAI models running behind the scenes.

But here's the thing: every prompt your team sends and every response the model generates flows directly to OpenAI. You have no visibility into what's being sent, what it costs, or whether sensitive data is leaking out in the process. Multiply that across a team of developers, and you've got a real blind spot.

We built a fix for this. Starting today, you can route all Cursor traffic through Grepture.

What this gives you

See every request

Every Cursor interaction — prompts, completions, inline edits — gets logged in your Grepture dashboard. Search by content, filter by developer, trace multi-turn coding sessions from start to finish. When something goes wrong or a completion produces unexpected results, you can see exactly what happened.

Know what it costs

Cursor burns tokens fast. Tab completions, chat messages, inline edits — each one is an API call with input and output tokens. With Grepture in the path, you get per-request cost attribution: which model was used, how many tokens, and what it cost. Roll that up by developer, by day, by project. No more guessing where the budget went.

Protect sensitive data

Developers work with code, config files, error logs, and database output — all of which Cursor sends as context to OpenAI. That context often contains API keys, customer data, internal URLs, and credentials. Grepture's detection rules scan every outbound request and catch sensitive data before it reaches OpenAI — the same rules that protect your production API traffic.

Setup takes 2 minutes

No SDK to install. No code changes. Just one URL in your Cursor settings.

In Cursor, go to Settings → Models → Override OpenAI Base URL and paste:

https://proxy.grepture.com/cursor/grp_your-key-here/v1

Replace grp_your-key-here with your Grepture API key from the dashboard.

That's it. Every Cursor request now flows through Grepture. Open your dashboard to see the traffic.

How it works under the hood

Cursor supports an Override OpenAI Base URL setting that redirects all API calls to a custom endpoint. The Grepture proxy accepts these requests at /cursor/<greptureKey>/v1, extracts your Grepture API key from the URL path, applies your detection rules, and forwards the request to https://api.openai.com/v1/chat/completions with your OpenAI key.

The /cursor/<greptureKey> prefix is stripped before forwarding, so OpenAI receives a standard API request. Cursor sends your OpenAI API key via the Authorization: Bearer header automatically — Grepture passes it through unchanged.

On the way back, the response flows through Grepture — logged, measured, and (if you have PII rules enabled) scrubbed of any sensitive data that made it into the response.

Latency impact is minimal. The proxy adds under 10ms to each request — negligible compared to the model inference time.

Team setup

For teams, share the base URL with your Grepture team API key. Each developer pastes it into their own Cursor settings. This gives you one dashboard view of all Cursor usage across your organization.

Some things you can do with this:

  • Budget tracking — see total Cursor spend per developer, per week
  • Prompt auditing — review what's being sent to the model across your team
  • Data protection — enforce the same PII and secret scanning rules you use in production
  • Debugging — when a developer says "Cursor did something weird," you can pull up the exact conversation

What's next

This is our second AI coding tool integration, following Claude Code. Cursor was the natural next step — it's widely used, it supports base URL configuration, and the observability gap is just as real.

We're looking at more AI coding tools next. If you're using Copilot, Windsurf, or other tools and want the same visibility, let us know.

Get started

  1. Create a Grepture account (free plan includes 1,000 requests/month)
  2. Paste the base URL into Cursor's Override OpenAI Base URL setting
  3. Open the dashboard and watch your traffic flow in

Full setup guide in our docs.