Plaid's Auth product is billed under the one-time fee pricing model. This means that you will incur charges for the Auth product whenever an Item is initialized with Auth. This occurs when an Item has been successfully created by Link and the Auth product was included in Link's product array. An Item is typically considered successfully created once the public_token returned by Link is exchanged for an access_token. For micro-deposit Auth flows, the Item may be considered created — and the Auth fee incurred — once the public_token is created, which can happen before an access_token exists.
If the Item was not initialized with the Auth product at the time of creation, it can also be initialized later by calling the product endpoint belonging to the Auth product - /auth/get - on the Item.
For one-time fee products like Auth, it does not matter how many API calls are made for the Item; the cost is the same regardless of whether the product's endpoints are called many times or zero times.
Auth requires the Item to be healthy. Auth will not be billed if it is called on an Item that is in an unhealthy state. You can check an Item's health by calling /item/get and inspecting the item.error field.