Using own API keys (O1) fails in Composer but works in Chat!

Bug Report
1

There are a few issues related to this this but I haven’t seen the problem explicitly addressed yet.

I am a Cursor Pro paid user:

I have an OpenAI API Key and as a Tier 5 user, I have O1 API access.

I have enabled and verified my OpenAI API Key in Cursor but if I attempt to use it via Composer i get an error:

Usage Based Pricing is required

Due to low rate limits during the preview period, usage-based pricing is required to use o1. Please enable usage-based pricing.

I should not need usage-based pricing; I’m trying to use my own keys.

Weirdly if.I try to use Chat instead of Composer, it does work with my O1 API..

Any help is welcome!

2

I’m not sure that Composer supports o1 usage yet, even if you have access to the API key. This would require some integration on Cursor’s part, since it’s not a 1:1 replacement with GPT-4o.

3

Hey, Composer doesn’t support your API keys. It only works with models from your subscription.