Skip to main content

​
Overview

Usage is where you review saved AI activity and manage AI Puffer credits. In WordPress admin, go to AI Puffer > Usage. Cloud account controls appear in Overview, and hosted requests in Requests. Saved conversations remain available in the local logs. Visitor billing, pricing rules, balances, and WooCommerce packages are separate controls; their layout can vary by plugin version.
Cloud credits fund hosted requests on your connected AI Puffer account. Visitor credits are WordPress user balances you manage for access to your tools. A visitor purchase does not increase your Cloud balance. Your own provider models use the provider’s billing instead of Cloud credits.

​
Cloud overview and requests

  1. Open AI Puffer > Usage > Overview.
  2. Review available credits, the free monthly allowance, included plan credits where applicable, their renewal dates, and purchased credits.
  3. Use Refresh after a purchase or account change. Opening Usage also refreshes the balance in the background.
  4. Use Buy credits for optional Freemius top-ups. Check the buyer email before paying.
  5. Open Requests to see Cloud model names, status, token usage where available, and credits used.
Available, free, and purchased Cloud credit balances
The screenshot shows an example account without an included plan allowance. Eligible verified accounts receive 25 free credits per month. Pro Plus includes 3,000 AI credits monthly and Pro Max includes 10,000. Unused free and included credits expire each period; purchased credits do not expire. Balances are shared across sites on the same Cloud account. Whole-number balance displays are rounded; detailed request records may show decimals. See Plans and Credits. Use Edit next to the account email to update the AI Puffer/Freemius identity, or Disconnect to stop Cloud access for this site. See Cloud account controls. Text charges use tokens and a model-specific minimum. Media and embeddings use their operation-specific pricing. A model-picker estimate is not a guaranteed per-request price. Before a call, Cloud reserves enough for the allowed output; lowering the output limit may help if the reservation exceeds your remaining balance. Cloud request history is different from local conversation logs: BYOK requests are not Cloud charges. Knowledge indexed with a direct OpenAI embedding model therefore does not appear as Cloud activity, even when the storage provider is Local.

​
Visitor billing and local logs

The controls below manage your WordPress visitors and saved activity. They do not change Cloud model pricing or add Cloud credits. Some screenshots show the earlier Logs and Billing tab layout.

Logs

Search, inspect, export, delete, and retain saved activity.

Pricing

Define how model usage is converted into AI Puffer credits.

Activity

Review credits added, debited balances, and usage entries.

Balances

Edit user balances and reset periodic usage.

WooCommerce Integration

Sell credit packages and publish a customer dashboard.

Troubleshooting

Check common setup and billing issues.
Usage screen with Logs and Billing tabs
Key terms:

​
Logs

Open AI Puffer > Usage > Logs. Logs show saved activity from AI Puffer modules. Use them to review conversations, inspect request metadata, check vector search results, export records, and control retention.

​
Conversation Logs

Conversation logs store the saved message history for chatbot and other AI requests. Use filters to find the records you need, then open a row to inspect the full exchange. Click a row to open Conversation Details. The detail panel shows the full exchange, timestamps, provider and model metadata, usage tokens, request payloads when saved, and a delete button for that single log.
Usage logs with filters and conversation details

​
Vector Scores

When a chatbot, Content Writer request, or other AI request uses vector context, the assistant message can show a Score badge. The score shows how closely the retrieved content matched the user’s request. Click the badge to see the vector provider, source, score, and content preview.
Use scores to tune Knowledge Base retrieval. If useful content is not being used, lower the threshold or increase the result limit. If unrelated content is used, raise the threshold.
Scores explain retrieval quality. They do not grade the final AI answer.
Conversation details with vector score results

​
Export and Delete

To export logs:
  1. Open AI Puffer > Usage > Logs.
  2. Apply filters if needed.
  3. Open the actions menu.
  4. Click Export logs.
The CSV includes log ID, date, user, source, module, message count, token count, preview, and conversation UUID. To delete logs:
  1. Open AI Puffer > Usage > Logs.
  2. Apply filters if you only want to delete part of the log history.
  3. Open the actions menu.
  4. Click Delete logs.
  5. Confirm the action.
To delete one conversation, open the row and click Delete in Conversation Details.

​
Log Retention

Log retention automatically removes old logs. To configure it:
  1. Open AI Puffer > Usage > Logs.
  2. Click Set retention.
  3. Enable Auto-delete logs.
  4. Choose Delete logs older than.
  5. Save the setting.
Available retention periods:
The retention modal also shows the pruning schedule and last run time.
Log Retention modal

​
Billing

Open AI Puffer > Usage > Billing. Billing connects three things:
  1. Pricing rules decide how much a request costs in AI Puffer credits.
  2. Balances store prepaid credits for logged-in users.
  3. Quotas limit usage for guests, users, or roles when a balance is not enough.
For logged-in users, AI Puffer deducts from the credit balance first. If the balance does not cover the full request cost, the remaining usage is counted against the user’s quota. For guests, there is no persistent balance, so usage is checked against the guest quota.
Quotas are configured inside the module that uses them: Chatbots, AI Forms, or Images. The Usage screen shows and resets recorded usage, but it is not where you configure module limits.

​
Pricing

Open AI Puffer > Usage > Billing > Pricing. These visitor pricing rules decide what you charge WordPress users for a model operation. Cloud prices are set by the Cloud catalog and are charged independently.

​
How Pricing Works

Credits are internal AI Puffer units. You decide how many credits each request should cost. Use Flat when every request should cost the same amount. Use Per 1K Tokens when longer chat or form requests should cost more. Use Per Image or Per Video for media tools. For chat and AI forms, tokens are the pieces of text sent to and returned from the AI provider. Input tokens are the user message, instructions, and context sent to the model. Output tokens are the AI response. For xAI text requests, pricing rules use the token usage returned by the xAI response when it is available. For xAI image generation and image editing, AI Puffer records provider usage metadata when xAI returns it, but credit deduction still follows your configured image pricing rule such as Per Image or Flat. Example token rule: If a request uses 800 input tokens and 300 output tokens: AI Puffer rounds the result up, so this request is charged as 2 credits. Example flat rule: Every matching request costs 5 credits, no matter how long the prompt or response is. To create a pricing rule:
  1. Click New Pricing.
  2. Select Usage type.
  3. Select Provider & Model.
  4. Select Billing method.
  5. Enter the rate.
  6. Click Save Rule.
Billing Pricing tab
New Pricing rule modal
Supported usage types: Supported billing methods: Pricing rules can be enabled, disabled, edited, or deleted from the Pricing table.
If a matching pricing rule exists, AI Puffer uses that rule to estimate and record credit usage. If no rule matches, it falls back to the raw recorded usage units.

​
Activity

Open AI Puffer > Usage > Billing > Activity. Activity shows the ledger for the selected time range. Available ranges:
Summary cards: The ledger table shows time, actor, type, module/model, credit change, and usage units.
Billing Activity tab

​
Balances

Open AI Puffer > Usage > Billing > Balances. Balances is for logged-in WordPress users. Use it to search users, edit credit balances, review periodic usage, reset usage, and view purchase history. The table includes: To edit a balance:
  1. Search for the user.
  2. Edit Credit Balance.
  3. Press Enter or click outside the field.
AI Puffer saves the new balance and records the difference as an admin adjustment in the ledger. To reset usage:
  1. Click Details for a user.
  2. Click Reset usage for one scope, or Reset all for all scopes.
  3. Confirm the reset.
Resetting usage does not change the user’s credit balance.
Billing Balances tab
Billing Balances tab with periodic usage details

​
WooCommerce Integration

Open AI Puffer > Usage > Billing > WooCommerce. Use this tab to publish a customer dashboard and connect WooCommerce products to AI Puffer credits.
WooCommerce credit delivery requires a WordPress user account. Guest checkout orders without a linked user cannot receive credits automatically.
Customer dashboard:
  1. Create a WordPress page, such as Credits & Usage.
  2. Add this shortcode:
  1. Publish the page.
  2. Open AI Puffer > Usage > Billing > WooCommerce.
  3. Set Customer dashboard URL to that page.
  4. Set Default buy credits URL if you want dashboard buttons and quota messages to send users to a specific page.
The dashboard shows credit balance, recent purchases, and quota usage for Chatbots, AI Forms, and Images.
Billing WooCommerce tab
Shortcode options: Examples:
Credit packages:
  1. Open WooCommerce > Products.
  2. Create or edit a product.
  3. Find the AI Puffer: Credit Package box.
  4. Enable Sell this product as an AI Puffer credit package.
  5. Enter Credits Granted Per Quantity.
  6. Set the normal WooCommerce product price.
  7. Publish or update the product.
Credits are granted when the WooCommerce order becomes Completed. Quantity is multiplied by Credits Granted Per Quantity.
AI Puffer credit package box in WooCommerce product editor
If pricing rules exist, the product editor can show a rough package value, such as how many chat requests, form submissions, images, or videos the package may cover at current pricing.
Package previews are for sizing only. The real cost depends on the actual provider response, token usage, selected model, and matching pricing rule.

​
Troubleshooting

  1. Open AI Providers.
  2. Confirm the provider API settings are saved.
  3. Sync models for that provider.
  4. Return to Usage > Billing > Pricing and create the rule again.
Check these items:
  1. Confirm the visitor is logged in.
  2. Confirm the page contains [aipkit_token_usage].
  3. Check role access if role access is enabled.
  4. Confirm the related module has recorded usage for that user.
  5. Confirm the shortcode attribute for that module is not set to false.
Check these items:
  1. Confirm the WooCommerce order is completed.
  2. Confirm the user’s credit balance increased in Usage > Billing > Balances.
  3. Confirm the user is logged in.
  4. Confirm the module has a matching pricing rule.
  5. Confirm the request cost does not exceed the user’s remaining balance plus available quota.
  1. Open Usage > Logs.
  2. Click Set retention.
  3. Enable Auto-delete logs.
  4. Choose a shorter retention period.
  5. Delete old logs manually if needed.
  1. Open Usage > Billing > Activity.
  2. Select a date range that includes the change.
  3. Check whether the balance was changed from Usage > Billing > Balances or through a completed WooCommerce order.
Manual balance edits and completed credit package orders create ledger entries.