Q: End user rate limit on external websites
When embedding AgenticFlow agents as widgets or apps on an external website, is there a way to set rate limits or usage quotas for end users?
Specifically, can I restrict how many times or how frequently an individual user (or IP) can trigger the agent, to prevent abuse or excessive credit consumption?
If yes, how granular is this control (per day, per month...?), and is it configurable from within the AgenticFlow dashboard?

SeanP_AgenticFlowAI
May 23, 2025A: Hey Thomas8Way,
That's a really important question for managing embedded agents and controlling usage!
Currently, AgenticFlow does not have a built-in, user-facing feature directly within the dashboard to set granular rate limits or usage quotas per individual end-user (or IP address) interacting with an embedded agent widget or app on an external website.
Our current rate limiting is primarily at the workspace/account level for overall API calls to prevent system-wide abuse, and credit consumption is tracked at the workspace level.
How to Approach This Currently & Future Considerations:
1. Your Application Layer (If using API/Boilerplate):
If you're using our API to build a custom frontend for your agent (e.g., with the Next.js boilerplate: https://github.com/PixelML/agenticflow-boilerplate), you would implement end-user rate limiting and session management within your own application's backend logic.
Your application would authenticate/identify users (or track IPs), count their interactions with your AgenticFlow-powered backend, and then decide whether to proxy their request to AgenticFlow or block it based on your defined limits.
2. For Standard Widget Embeds (More Limited):
With the direct script embed for the chat widget, there's no direct mechanism within AgenticFlow to say "User X from IP Y can only chat 10 times today."
You could potentially implement some client-side JavaScript on your website to try and limit widget interactions from a single browser session, but this is less robust and can be bypassed.
3. Roadmap Feature - Granular Usage Controls:
This is a very valid and needed feature, especially for public-facing agents. The ability to set per-user, per-IP, or per-session limits on embedded agents is definitely something we see the value in.
Please add this as a specific feature request (or vote if it exists) on our public roadmap: https://agenticflow.featurebase.app/. Title it something like "Per-End-User Rate Limiting/Quotas for Embedded Agents." The more community demand we see, the higher we can prioritize it.
In short:
- No direct, built-in dashboard controls for per-end-user rate limiting on embedded widgets yet.
- If using our API for a custom app, implement rate limiting in your application.
- This is a key area for future development, so please make your voice heard on the roadmap!
We understand the importance of preventing abuse and managing costs for publicly accessible agents, and we'll be looking to enhance these controls.
— Sean