Cursor API Key Management

Overview

Manage any Cursor BYOK/provider credentials as individual, least-privilege secrets with approved routing, ownership, rotation, spending limits, and exposure response.

Prerequisites

• An approved provider/model route, named key owner, secrets-manager integration, and budget policy.
• Confirmation that BYOK is permitted for the intended data classification and tenant configuration.

Instructions

1. Issue one scoped key per owner or approved service through the provider/secrets manager.
2. Configure it through the approved UI/injection path; never commit it, paste it into rules, or share it between users.
3. Set provider spending/rate controls, review usage, and rotate on schedule or suspected exposure.
4. Revoke first, then investigate, when a key is lost, leaked, or no longer required.

Output