Being charged for failed o1-preview requests

Bug Report
,
1

I have requests that fail from o1 preview (2 so far) that showed up as a $0.40 usage based charge on my account

I don’t mind failures give the beta nature but I should not be charged for a failed call, and this is currently 2/8 calls made

4 Likes
2

I have 2/3 failed requests. First request worked fine but butchered my code with putting # ... existing code ... everywhere. I’m not asking for the $0.80 back, I’ll just take a break from testing it for now.

1 Like
3

I kept trying and they’re failing 100% of the time now.

4

Hi @sixteenstudio

You are right, the Cursor team is aware of the problem. You can write to: hi@cursor.com to get a refund.

1 Like
5

Thanks for your help. It’s only 2 requests so far as far as I know. If it begins to happen frequently, I’ll send an email!

6

I can confirm it was just happening intermittently. It’s working fine now.

7

I still have the problem. o1-mini works though

8

This is happening using API as well. I can see my openrouter being charge but o1-preview output is not being render.

9

I’ve also had several failed “o1-preview” calls show up on my billing and it adds up quickly since each call costs €0.40. It would be great if failed calls didn’t count towards the balance automatically. Is there any plan to update the billing so that unsuccessful requests are filtered out? It would save a lot of time if this was handled without needing to contact support for each case :pray: