> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/email-quota.md).
# Email Quota
Learn what email quota limits apply to accounts.
Humanic regulates email volume in two ways:
1. email volume (quota)
2. sending rate
These limits help improve your deliverability and likelihood of reaching your recipient’s inbox.
### [](https://resend.com/docs/knowledge-base/resend-email-quota#free-account-daily-and-monthly-email-quota)Free Account Daily and Monthly Email Quota
Free accounts have a daily email quota of 100 emails/day and 3,000 emails/month. This quota includes both sent and received emails. Multiple `To`, `CC`, or `BCC` recipients in sent emails count as separate emails towards this quota.
### [](https://resend.com/docs/knowledge-base/resend-email-quota#paid-plan-email-quota)Paid Plan Email Quota
* Humanic plans have no email quota limits.
* Multiple `To`, `CC`, or `BCC` recipients in sent emails count as separate emails towards the monthly quota.
### [](https://resend.com/docs/knowledge-base/resend-email-quota#rate-limits)Rate Limits
All accounts start with a rate limit of 2 requests per second. The [rate limits](https://resend.com/docs/api-reference/introduction#rate-limit) follow the [IETF standard](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers) for stating the rate limit in the response header. If you have specific requirements, to request a rate increase send an email to
### [](https://resend.com/docs/knowledge-base/resend-email-quota#bounce-rate)Bounce Rate
All accounts must maintain a bounce rate of under **4%**. The [**Metrics page**](https://resend.com/metrics) within an account and/or [webhooks](https://resend.com/docs/dashboard/webhooks/event-types#email-bounced) allow you to monitor your account bounce rates. Maintaining a bounce rate above 4% may result in a temporary pause in sending until the bounce rate is reduced.
Tips to keep a bounce rate low:
* Remove inactive user email addresses from email lists.
* Only send to recipients who have given consent to receive email.
* When testing, avoid sending to fake email addresses.
* If you are using open/click tracking, periodically remove recipients who are not engaging with your emails from your email lists.
### [](https://resend.com/docs/knowledge-base/resend-email-quota#spam-rate)Spam Rate
All accounts must have a spam rate of under **0.08%**. The [**Metrics page**](https://resend.com/metrics) within an account and/or [webhooks](https://resend.com/docs/dashboard/webhooks/event-types#email-complained) allow you to monitor your account spam rates. Maintaining a spam rate over 0.08% may result in a temporary pause in sending until the spam rate is reduced.
Tips to keep a spam rate low:
* Give recipients an easy way to opt-out of emails.
* Send relevant and timely emails.
* Only send to recipients who have given consent to receive email.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/email-quota.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.