Credits System is currently in beta.
This means the model, credit costs, and available features may evolve over time as we continue improving Feedier.
Overview
Feedier uses a credits-based model to reflect the value we bring to you on the platform and align it to our business model.
Credits are:
Consumed when you use AI-powered features that create value
Automatically reimbursed when AI results are rejected
In this way you pay for the value Feedier brings to you
The Credits Usage page gives you full transparency into how credits are used across your organization and teams.
When credits are used (and reimbursed)
Credits are used when you:
Create an Action Plan
Automatically generate a Saved Report (coming from automations)
Run Feedback Analysis
Accept an Agent Recommendation
Credits are reimbursed when you:
Reject an AI-generated result
Give a thumbs down to an Action Plan
Reject an Agent Recommendation
AI Summary does not consume credit at the moment but it will in next iterations
How many credits each feature uses
Here’s how credits are consumed per action:
Feature | Credits used |
Action Plan creation | 0.50 credit |
Automatic Report generation | 0.50 credit |
Agent Recommendation (accepted) | 0.25 credit |
Feedback Topics Analysis (per 100,000 feedbacks analyzed) -> Re analyzing verbatims also spends credits | 25 credits |
Concrete examples
1 credit = 2 Action Plans
1 credit = 2 Reports
1 credit = 4 accepted Recommendations
25 credits = 100,000 feedbacks analyzed
You only spend credits when the output is accepted and kept.
Credits Usage page
The Credits Usage page gives you a complete overview of your organization’s consumption.
Organization summary
At the top of the page, you’ll see:
Total credits available
Total credits consumed
Remaining credits
This gives you an instant snapshot of your overall usage.
Team breakdown
Each team has its own credits usage view, allowing admins to monitor and control consumption.
For each team, you’ll see:
Team name
Credits consumed
Credits remaining (based on the team limit)
Team limits
Admins can set a credit limit per team
A team limit cannot exceed the remaining organization credits
Once a team reaches its limit, credit-consuming actions are blocked for that team
This helps prevent overuse and ensures fair distribution across teams.
Credits transaction table
The transaction table shows every credit-related action, in full detail.
Each row includes:
Object
(Action Plan, Report, Analysis, Recommendation, etc.)Status
Accepted or RejectedCredits impact
Positive number → credits consumed
Negative number → credits reimbursed
User who triggered the action
Remaining balance after the transaction (running total)
This makes it easy to audit usage and understand exactly how credits are spent.
Out of credits
If your organization runs out of credits:
Credit-consuming actions are blocked
Users see an Out of credits message explaining why the action can’t continue
Credits never go negative
Team limits are always enforced