Webeyez AI Credits
Overview
This page explains how credits are consumed when using Webeyez tools.
Core rule: Each time a tool runs, it counts as 1 credit, with the exception of Webeyez internal tools, which are free (0 credits).
Credits are shared across the organization. All users belonging to the same organization draw from a single shared credit pool, so consumption by one user reduces the balance available to everyone else in that organization.
Credit Rules
Tool Name | Purpose | Credits |
Check webeyez status | checks status and returns the final AI response when complete | 0 |
Get organization domains | Get the list of available domains for a specific organization, used to match the exact domain to query | 0 |
Get organizations list | Get the list of organizations the current user has access to (always the first step in the query process) | 0 |
Get session recording links | Retrieves shareable session recording links for up to 10 sessions at once (given an organization ID and an array of session IDs) | 1 |
Logout webeyez | Remove the saved Personal Access Token (PAT) to log out of Webeyez; restarts the server | 0 |
Start webeyez query | Start a long-running AI query on Webeyez performance analytics data for a given organization and domain | 1 |
Submit feedback | Submits positive or negative feedback on a specific query response (identified by message ID). | 0 |
What Counts as a Credit
- Billable (1 credit each): any tool run that performs data work, running an AI query and checking/retrieving its status.
- Free (0 credits): Webeyez internal tools used for setup, navigation, and account management (listing organizations, listing domains, and logging out).
Notes
- Credits are charged per tool run, not per conversation. A single question that requires starting a query and then polling its status one or more times will consume 1 credit for the start plus 1 credit for each status check.
- Credits are shared at the organization level, every user in the organization spends from and depletes the same pool. Coordinate usage across the team to avoid unexpectedly exhausting the shared balance.
- Internal/lookup tools are intentionally free so that resolving the correct organization and domain before a query does not cost credits.
- Failed or empty runs of a billable tool still count as a run; plan queries carefully to avoid unnecessary consumption.
Tips to Minimize Credit Usage
- Resolve ambiguity (organization, domain, date range) before starting a query, using the free internal tools.
- Batch related questions into a single well-formed query where possible rather than issuing multiple separate queries.
- Avoid redundant status checks, poll only as needed until the job completes.