Support
Tier Guide — Free, Pro & Max
Three tiers, one API endpoint, same 10 tools. The only difference is request volume and support level.
Quick comparison
Free Pro Max
$0/mo $7/mo $19/mo
───── ───── ─────
555 req/mo 3,500 req/mo 10,000 req/mo
3 backends 10 backends 20 backends
Unlimited keys Unlimited keys Unlimited keys
Full access Custom scopes Custom scopes
Community Email support Priority support
No trial 7-day free trial No trialThe endpoint https://zephex.dev/mcp and all 10 tools are identical across tiers. You can use find_code, read_code, check_test, keep_thinking, etc., on every tier.
What counts as a request?
Every tool call from your AI agent counts as one request. The tools/list handshake (which lists available tools) does not.
Counted as requests NOT counted ────────────────────────────────────────────────────────────── find_code(...) tools/list (initial handshake) read_code(...) Editor reconnecting check_test(...) Test Pulse / health checks get_project_context(...) Failed auth (rejected before counting) explain_architecture(...) keep_thinking(...) audit_headers(...) check_package(...) project_memory(...) Zephex_dev_info(...)
So if you ask your agent "find where validateToken is used" and it calls find_code twice and read_code once, that's 3 requests.
Free tier (555 requests/month)
Generous enough to evaluate Zephex on real work. The 555 requests refresh on the 1st of every month.
What 555 requests gets you
- ~10 requests/day on average
- ~30-50 small coding sessions per month
- Or ~5-10 deep refactor sessions (uses ~30-60 requests each)
- Plenty for a side project or trying it on a hobby repo
Free tier limits
- 3 MCP backends — Zephex itself counts as one. You can add 2 more (e.g. a Stripe MCP, a Supabase MCP).
- Unlimited API keys — one per editor, project, or environment with no cap.
- Full access — every tool is available. No feature locks.
- Community support — replies as fast as we can, but no SLA.
What happens when you hit 555?
The next request returns HTTP 429 with a Retry-After header set to the next month boundary. Your agent will see an error in its tool call. Easy fix: wait until the 1st, or upgrade.
Pro tier ($7/month, 3,500 requests)
The everyday-developer tier. Roughly 12x the request volume of Free. Comes with a 7-day free trial — no card required to try it.
What 3,500 requests gets you
- ~115 requests/day on average
- ~5-10 hours of agent-assisted coding per day
- Enough for a daily driver across multiple projects
- Won't hit the cap unless you're pair-programming with the agent for 8+ hours daily
Pro tier upgrades
- 10 MCP backends — connect Stripe, Supabase, AWS, GitHub, plus your own.
- Unlimited API keys — one per project, one per editor, one per teammate, no cap.
- Custom key scopes — restrict a key to specific tools (e.g. read-only key for CI).
- Email support —
support@zephex.dev, typically <24h response. - 7-day free trial — full Pro features, no card required, cancel anytime.
How the trial works
Click "Start Pro Trial" in the dashboard. You get 7 days of full Pro access (3,500 requests, all features) without entering payment info. After 7 days, you either:
- Add a payment method to continue on Pro
- Or auto-revert to Free (555/month, 3 backends, unlimited keys)
No surprise billing — if you don't add a card, you're back on Free automatically.
Max tier ($19/month, 10,000 requests)
For heavy users — agent-driven workflows, large refactors, multi-repo work. Roughly 33x Free.
What 10,000 requests gets you
- ~330 requests/day on average
- Enough for non-stop agent use during work hours
- Multi-repo refactors, large architecture migrations, code reviews at scale
- Multiple developers sharing one account
Max tier upgrades
- 20 MCP backends — twice Pro's limit.
- Unlimited API keys + custom scopes.
- Priority email support — typically <6h response.
- Same endpoint, same tools, just more headroom.
How to check your usage
From the CLI:
# All keys, all editorsnpx zephex usage # Just one editornpx zephex usage --cursornpx zephex usage --claudenpx zephex usage --vscodeExample output:
mcp_prod_pri…4f32 (pro) Used by: Cursor (global), Claude Code (global) Today 17 calls This month 423 / 3500 ████░░░░░░░░░░░░░░░░ 12% By tool (this month): find_code 142 ███████████████ read_code 89 █████████░░░░░░ check_test 67 ███████░░░░░░░░ keep_thinking 51 █████░░░░░░░░░░ explain_architecture 28 ███░░░░░░░░░░░░From the dashboard:
https://zephex.dev/dashboardLive charts of requests/day, requests/tool, time-of-day patterns. Updates within 60 seconds of every tool call.
Visual: when to upgrade
Are you hitting the monthly cap?
│
┌────────┴────────┐
YES NO
│ │
▼ ▼
On Free? Stay on current tier
│
┌──────┴──────┐
YES NO (you're on Pro/Max)
│ │
▼ ▼
Try Pro Upgrade Pro → Max
free trial or wait for 1st of monthSigns it's time to upgrade
- You're seeing "429 Too Many Requests" in your editor
npx zephex usageshows you at 80%+ of monthly limit before mid-month- You want custom key scopes (restrict keys to specific tools)
- You need to connect more than 3 MCP backends
- You want faster support replies
Signs you can stay on Free
- You only use Zephex on one project
- You're using < 200 requests/month
- You don't need additional MCP backends
Rate limits
Zephex applies a sliding-window rate limit per API key (powered by Upstash Redis):
Tier Per minute Per hour Per month ───────────────────────────────────────────────────── Free 50 200 555 Pro 300 1,000 3500 Max 1,000 2,000 10000
If you blow past the per-minute limit (rare during normal coding), you'll get a 429 with a Retry-After header. Wait the suggested time and continue.
Billing details
Payment
- Cards processed by Stripe (PCI-compliant)
- Major cards accepted (Visa, Mastercard, Amex, Discover)
- USD only currently
How charges work
- Pro — $7/month, charged on the 1st
- Max — $19/month, charged on the 1st
- Prorated when you upgrade mid-month (Pro → Max)
- Cancellation takes effect at the end of the current period (no immediate cutoff)
Receipts and invoices
Every charge generates a receipt by email and is available in the dashboard. PDF invoices on request: support@zephex.dev.
Refunds
Email support@zephex.dev within 14 days of a charge for a full refund, no questions asked.
Key scopes (Pro and Max only)
Pro and Max accounts can restrict an API key to specific tools. Useful for:
- A read-only key for a CI pipeline (only
find_codeandread_code) - A team member who should only see web tools (
audit_headers,check_package) - A project-specific key with a smaller tool set
You can also restrict from the CLI side using npx zephex tools --enable a,b,c — see Tool Filtering.
FAQ
Does the free tier ever expire?
No. Free is permanent. Use it forever if it fits your workflow.
Do unused requests roll over?
No. Limits reset on the 1st of every month.
What if I cancel mid-month on Pro?
You keep Pro access until the end of the current billing period, then revert to Free.
Can I switch between tiers?
Yes, anytime. Upgrades are immediate (prorated). Downgrades take effect at the end of the current period.
Do API keys expire?
No, but you can revoke any key from the dashboard or via npx zephex disconnect. Revoked keys stop working immediately.
What if my agent calls a tool that fails?
Failed calls (4xx errors) don't count toward your monthly limit. Successful calls do.
Where to next
- Plans Overview — table comparison
- Usage Limits & Caps — rate-limit details
- Usage & Analytics — dashboard charts
- CLI Commands — including
zephex usage --editor - API Key Management — creating, revoking, scoping keys