Skip to content

Cursor BYOK provider billing

Cursor BYOK contributes provider billing and usage-export rows for AI API usage that originates from Cursor-managed bring-your-own-key workflows.

Release state

This guide documents the read-only cursor_byok connector implemented in the platform connector surface.

Required access

Grant read-only access to:

Scope Purpose
provider_billing.readonly Read provider billing export rows.
provider_usage_metadata.readonly Read usage metadata needed for attribution context.

Do not grant key creation, key deletion, spend-limit mutation, or provider administration scopes.

Setup

  1. Enable provider billing exports for the Cursor BYOK provider accounts.
  2. Create a read-only integration credential for those exports.
  3. Store the credential reference in Venturi.
  4. Set ARGMIN_CURSOR_BYOK_LOOKBACK_HOURS if you need a poll window other than 24 hours.
  5. In Venturi, open Administration -> Connectors -> Cursor BYOK and run Test connection.

Verification

  • Provider billing rows appear in the latest sync.
  • Usage metadata identifies the API product or service name where the provider exposes it.
  • Cursor BYOK usage joins to owner or team context only where matching evidence exists.

Rotation and offboarding

Rotate the export credential on the provider account schedule. Removing the connector stops new Cursor BYOK billing correlation.