When using the o1 model, if I attach an image, it shows an error message stating that “the image cannot be used,” but $0.4 is still charged. I understand that the API usage fee might not have been applied in this case. I would like to suggest implementing a system where charges are not incurred for failed requests caused by such errors.
5 Likes
looking into this right now!
like you say, we shouldn’t charge for errored requests, so this might be a bug on our end
3 Likes
May we please revisit the request to have our Composer Agents having full access to our resource consumption and should be able to spit out and update a standard dashboard in a .RMD file whenever asked “consumption?” and have it auto_update “20241227_cursor_resource_usage_report.rmd” or simply “2024_12_cursor_resource_usage_report.rmd”
yes, we should probably add some way to see usage data within the app itself! for now i do think having it in the settings would make it most accessible for most people