The AI label suggestions in the plugin use two separate things: an AI provider key that you supply, and TenthLoop credits. This article explains how each one works.
Your AI provider key
The AI runs in TenthLoop, using your own key with your own AI provider. Your provider bills you directly for that usage. It is separate from TenthLoop credits.
You manage the key from the AI Provider section of the integration in the TenthLoop portal. You can register or update the key, test the connection, and revoke it. Revoking removes the key only. Your tokens and other settings stay.
- Google Gemini is the provider you can choose today.
- You can optionally set a model and a maximum response length.
- The key is stored encrypted, one per workspace, and only the last four characters are shown afterwards.
- The key lives in TenthLoop, not on your WordPress site. The plugin settings only show whether a provider is configured and let you jump to the portal to change it.
To manage the provider settings from the plugin connection, the token needs the Websites (write) permission. See Installing and connecting the WordPress plugin.
What credits pay for
Credits pay for the remediation service when the plugin generates labels. You are charged only for labels that were actually generated, and only when the request succeeds. If the AI key is missing or rejected, nothing is charged. Credits belong to the workspace, so everyone on it draws from the same balance.
For what credits cost and how to get more, see tenthloop.com/pricing and What credits are for.
Before you remediate
Before AI labels are generated in bulk, the plugin shows a confirmation with the number of elements, what will be remediated, the cost per element, the total and your balance. Check it before you continue.
If your balance runs low
If you do not have enough credits for every selected element, the plugin fills in as many as you can afford, in the original order, and skips the rest. The confirmation tells you how many were skipped. If you cannot afford any, the request is declined and nothing is charged. Add credits and run it again for the remaining elements. There is no queue, so nothing runs later on its own.
If a request is retried after a dropped connection, you are not charged twice for the same labels.