Cursor staffs an in-house metering + billing org
Open roles — a dedicated Billing engineer building the usage-metering pipeline (raw events → invoiced amounts in Stripe), a Senior Staff Finance Systems engineer, and ~10 RevOps roles — show Cursor building the meter behind its seat-plus-usage pricing while buying payments.
A Software Engineer, Billing posting describes implementing “usage and billing systems changes end-to-end, from raw usage events at the edge to invoiced amounts in Stripe, including the metering pipeline” — i.e. Cursor builds its metering layer in-house and uses Stripe as the system of record for invoicing. Alongside a Senior Staff Finance Systems engineer and ~10 RevOps roles, it marks a deliberate build-out of the monetization machinery behind Cursor’s seat-plus-usage-pool model. Logged from public job postings via the wiki-signals pipeline.
Cursor's docs cut GPT-5.6 Luna's per-token rate roughly 80% (input $1 to $0.2, cache write $1.25 to $0.25, cache read $0.1 to $0.02, output $6 to $1.2 per million tokens) and GPT-5.6 Terra's roughly 20% (input $2.5 to $2, output $15 to $12), passing third-party API price cuts straight through to the dollar-denominated Other Models pool. Plan-level pricing was unchanged.