We have two separate accounts with different registrations, but after some recent updates to the API key section, we’ve run into a problem. All of our billing is now being charged to one account, even though we haven’t made any changes to the API keys in our systems. We double-checked, and the keys were indeed unchanged. To fix this, we created new keys and updated them everywhere. This situation is concerning because it could mean we might end up paying for charges that aren’t ours. Could you please investigate this issue and let us know what happened? We would appreciate your prompt attention to this matter.
Forum members cannot access your account. There is no scenario where we couldn’t blame the issue on misconfiguration or settings on your part, fortunately, so you should be able to investigate where this is arising.
First, are these accounts completely separate, or has one organization invited another account to its “team”? This is one source of possible cross-billing, as organization readers can set their default billing of user keys in the user interface, or billing of API calls by specifying an organization header.
I would look at the environment variables where keys are being used, and ensure you have matching and consistent OPENAI_API_KEY, OPENAI_ORG_ID and OPENAI_PROJECT_ID that all match the target to be billed. Then if you are not actually using or needing the features of organization members, remove all but owner from your account.
You can distribute an API key to sub-users for more controlled use than by inviting members to an org, by setting model, endpoint, and rate limits on the project and its API key.