AI Agent Access: Limits and Plans
How plans, monthly messages, daily limits and request rates apply to AI agents on your site, your AI assistant and the API.
This page explains what limits the three ways AI reaches NovixAgent AI are held to, what happens when one is reached, and where to read the numbers that apply to you. The three doors are AI agents on your site (AI Agents on Your Site), Your AI assistant (Your AI Assistant) and the API (API Keys and Connected Apps). Figures are not typed on this page: they come from the plan catalogue our servers read, and the table in What each integration allows, by plan is generated from it.
Which plans include what
The doors are part of the plan, like the other integrations. The table in What each integration allows, by plan shows which plans include them.
- AI agents on your site and Your AI assistant are offered through the plan's API and AI app access feature. Some of the actions an AI agent may use depend on another feature of the plan: appointments need booking, order lookups need the online store integration and enquiries need lead capture. An action your plan does not include shows that on its row in the tile.
- The API is switched on per plan. The API tile shows a lock on a website whose plan does not include it, and a key that points at such a website is refused with
PLAN_TIER_TOO_LOWwhile it stays listed. When the website moves to a plan with the API, the same key works again. - Plans are decided per website, so one account can have the API on one website and not on another.
Monthly messages
A website has one pool of monthly messages for its plan, and each way your assistant answers draws on it: your visitors in the chat, customers' AI agents, your own AI assistant, and chat requests sent with an API key. When the pool is used up the website goes into contact-only mode, as described in Billing & Plans, and an AI assistant or key that asks for an answer is told that the monthly messages are used up.
Customers' AI agents do not get the full pool. They draw on a share that is set aside for them, so a busy agent does not use up the messages your visitors need. When that share is used up, agents are turned away and your visitors are still served. Your own AI assistant and your own keys can use the full pool: they are yours.
Enquiries, bookings and order lookups
- Daily limit. You set the most enquiries, and the most bookings, that AI agents may send in a day, in Daily limit on enquiries and bookings on the tile. The allowed range is shown beside the field, and an empty field uses the default. Beyond the limit, AI agents are turned away until the next day.
- Plan allowances. Bookings and order lookups from AI agents count toward the same monthly allowances as those made in your chat, and agents use only a share of each, as with messages. Leads follow the plan's lead rules: Lead Capture.
- Spam protection. Further limits per person and per AI app apply on top, so that a bot does not fill your inbox or your calendar. A repeat enquiry from the same person on the same day adds no new contact. We do not publish the numbers of these protections, because publishing them would help the people they are meant to stop.
Request rates
Each API key and each connected AI app is held to a number of requests a minute for one website. A second limit applies to the account across its connections, so one busy integration does not starve the rest. The first number depends on the website's plan, and your software can read it from the X-RateLimit-Limit header of a response, together with X-RateLimit-Remaining and X-RateLimit-Reset.
When a limit is reached the call does not run, and the answer is RATE_LIMITED with a Retry-After header. A short burst of calls at the same moment can get CONCURRENCY_LIMIT instead: the service is busy with other calls, and a retry after the time given is enough. Customers' AI agents are held to rates for each AI app and for each website, which protect your site from a flood from one source.
Domain verification checks
Check now is limited for each website. If you press it too often, the screen tells you how long to wait. Waiting a few minutes after you publish a DNS record is the usual need: Verify Your Domain for AI Agents.
What you see at a limit
| Limit | What the AI agent is told | Where you see it |
|---|---|---|
| Monthly messages used up | It is turned away; try later | Monthly messages used up under Turned away in What AI agents did |
| Too many requests in a minute | RATE_LIMITED with a wait |
Too many requests in a minute |
| Daily limit on enquiries or bookings | It is turned away until the next day | Daily limit reached |
| A repeat enquiry from the same person | It is told the enquiry was received, and no new contact reaches you | Repeated enquiries from the same person |
| Order-lookup limit | It is told to try later | Order-lookup limit reached |
| The limit store is unreadable | The call is refused | Temporarily unavailable |
Where to read your usage
- Monthly messages and plan allowances: the usage meter described in Billing & Plans, and Website Analytics.
- What customers' AI agents did and what was turned away: What AI agents did on the AI agents on your site tile.
- What an API key did: Usage on the key's row in Dashboard → Account → API keys and AI apps.
- Your connections: the same list shows each key and app, and when it was last used.