Free vs Paid Tiers
Relevant source files
The following files were used as context for generating this wiki page:
e-zer0 operates on the Cloudflare Developer Platform. The distinction between Free and Paid tiers refers to the underlying Cloudflare Workers plans that host the e-zer0 instance. These tiers determine the operational limits for request volume, database interactions, and AI capabilities.
Sources: README.md:104-106, wrangler.toml:1-10
Cloudflare Tier Comparison
The choice of Cloudflare plan impacts how e-zer0 handles Model Context Protocol (MCP) traffic and background tasks. All agents connected to an e-zer0 instance share the total request budget of the hosting Cloudflare account.
Operational Limits
The following table outlines the primary differences between the Cloudflare Free Tier and the Paid Workers Plan as they apply to e-zer0:
| Feature | Free Tier | Paid Tier ($5/mo) |
|---|---|---|
| Worker Requests | 100,000 daily | Significantly higher limits |
| Request Types | Includes discovery, keepalives, and retries | Includes discovery, keepalives, and retries |
| D1 Database | Separate allowance | Increased limits |
| Workers AI | Separate allowance | Increased limits |
| Vectorize | Separate allowance | Increased limits |
Sources: README.md:108-112, src/routes/settings.tsx:288-292
Request Consumption Flow
Every interaction with the e-zer0 instance consumes a portion of the Cloudflare request budget. This includes not only active tool calls (like reading emails) but also infrastructure-level communication.
This diagram illustrates how various agent activities contribute to the total request consumption of the Cloudflare account.
Sources: README.md:108-110, src/routes/settings.tsx:288-291, src/app.ts:46-48
Impact of Tier Limits on Agent Behavior
When an e-zer0 instance reaches its daily request limit, it enters a cooldown state. The specific error code and subsequent behavior depend on the Cloudflare platform enforcement.
Resource Exhaustion (Error 1027)
A confirmed Cloudflare Error 1027 signifies that the daily request budget is exhausted. In this state:
- You must pause all traffic to the instance, including keepalives and scheduled retries.
- Traffic should remain paused until the next midnight UTC (plus jitter).
- Operators must confirm recovery before resuming normal operations.
Sources: src/routes/settings.tsx:298-301
Rate Limiting and Brute-Force Protection
e-zer0 uses a KV-based rate limiter to protect sensitive endpoints regardless of the tier. This protects /login and /mcp/token routes from abuse.
The sequence diagram shows how the RATE_LIMITER binding enforces short-term limits on authentication endpoints.
Sources: src/app.ts:37-43, wrangler.toml:26-31, src/routes/settings.tsx:302
Capacity Planning for Agents
Mailbox count alone does not predict usage. Effective capacity planning requires monitoring the frequency of specific activities.
- Idle Sessions: One session pinging every 180 seconds consumes approximately 480 requests/day.
- Reduced Frequency: Increasing the interval to 1800 seconds reduces consumption to 48 requests/day.
- Concurrent Use: Total consumption scales linearly with the number of concurrent active sessions.
Sources: README.md:109-110, src/routes/settings.tsx:291-293
Recommendations for Free Tier Users
To maintain stable operation on the Cloudflare Free Tier:
- Reuse Connections: Avoid frequent reconnection or re-initialization.
- Minimize Keepalives: Use the longest supported idle interval in the MCP client settings.
- Avoid Retries: Do not use "stacked" retry loops that rapidly consume requests during provider outages.
- Selective Health Checks: Use the
/healthendpoint sparingly for liveness only.
Sources: src/routes/settings.tsx:293-297, src/app.ts:46-48
Summary of Tier Management
The Cloudflare Paid Tier provides the necessary headroom for high-volume automated agents or large-scale email processing. The Free Tier is suitable for light personal use, provided that agent keepalives and retry logic are strictly bounded to stay within the 100,000 daily request limit.