zephex
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
←BackSign in
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
Get started freeSign in
DocsAPIToolsEditorsChangelogHelp

GET STARTED

WelcomeQuickstartSetup videoMCP Q&A (learn)BlogWhat is MCP?Who is Zephex for?Plans & PricingZ-GASAB benchmarkBenchmark chart (live)Changelog

INSTALLATION

Web Terminal tools (plain English)Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Test Pulse (check test)Test Pulse commandsProject MemorySupply Pulse (supply)Supply Pulse commandsTerminal CLI referenceSlash commands (37 palette)Web Terminal (dashboard)Command CompassCLI commandsCLI in DockerCLI: All editors (one command)CLI: Crush, Hermes, ChatGPT, KiloOAuth & HTTP setupInstall overviewHTTP APISetup WalkthroughHTTP vs stdio

API & KEYS

API Key ManagementKey Naming & FormatAuthenticationKey Dashboard

CONFIGURATION

Universal RequirementsSupported EditorsHow It WorksArchitectureCLAUDE.md TemplateAGENTS.md Template

EDITORS28 guides

Supported EditorsVS CodeVS Code extension (Marketplace)Claude CodeCursorWindsurfJetBrains

PLATFORM

macOSWindowsLinux

TOOLS10 tools

Capabilities OverviewTools OverviewTool FilteringTool Workflowsget_project_contextread_codefind_codecheck_packageexplain_architectureZephex_dev_infocheck_testaudit_headerskeep_thinkingproject_memory

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7Zephex vs GitHub MCPZephex vs SmitheryMCP EcosystemMarkdown Access

SUPPORT

Help CenterMCP troubleshootingTeam rolloutFAQConnection IssuesRate LimitsDowntime & ErrorsBillingTier GuidePro & Max guideUsage LimitsUsage Analytics

LEGAL

System StatusTerms (summary)Privacy (summary)Data UseSecurityAuthenticationSecurityData HandlingPrivacy PolicyTerms of Service

Quick Links

API Reference

Complete API documentation

Troubleshooting

Common issues and solutions

Community

Join our Discord community

Plugins

Editor and CLI integrations

Pricing

Free, Pro, and Max plans

Enter
Zephex_devzephex-devzephexzephexhello@zephex.dev
© 2026 Zephex. All systems operational.

Support

Usage Limits & Per-Key Caps

Zephex enforces limits at three levels: monthly account quota, per-minute burst rate, and optional per-key monthly caps. This page covers all three, plus overage billing and top-up packs.

MONTHLY QUOTAS BY TIER
TierRequests/monthBurst (req/min)API KeysMCP Backends
Free55550Unlimited3
Pro ($7/mo)3,500300Unlimited10
Max ($19/mo)10,0001,000Unlimited20

Monthly quotas reset on the 1st of each month at 00:00 UTC. If you upgrade mid-cycle, the higher limit applies immediately for the remainder of the month.

WHAT COUNTS AS A REQUEST
  • Counts: Every tools/call that reaches the Zephex endpoint — regardless of tool, duration, or response size.
  • Does not count: tools/list, initialize, ping, and connection handshakes.
  • Failed requests: A request that returns an error from the tool still counts (the proxy processed it). Only requests rejected at the rate-limit layer before reaching a tool do not count.
BURST RATE LIMITS

Burst limits use a sliding-window algorithm. If you exceed the per-minute cap, requests are rejected with error code -32002 and a Retry-After header indicating when to retry.

  • Free: 50 requests per minute
  • Pro: 300 requests per minute
  • Max: 1,000 requests per minute

Burst limits exist to protect service stability. Normal interactive usage (an AI editor calling tools during a coding session) will never hit them. They primarily prevent runaway automation loops.

PER-KEY MONTHLY CAPS

Pro and Max users can set a monthly request cap on individual API keys. This prevents a single integration from consuming the entire account quota.

  • Set from Dashboard → API Keys → click the gauge icon on any key.
  • Cap range: 1 to 1,000,000 requests per month.
  • Set to "unlimited" (null) to use the full account quota.
  • When a key hits its cap, only that key is blocked — other keys continue working.
  • Per-key counts reset alongside the account monthly reset (1st of month, 00:00 UTC).

Example: You have a Pro account (3,500/mo) with multiple keys:

  • production — cap: 2,000
  • staging — cap: 500
  • personal — cap: unlimited

If production hits 2,000, it stops working. staging and personal continue until the account total reaches 3,500.

json
{  "jsonrpc": "2.0",  "error": {    "code": -32003,    "message": "Per-key monthly cap reached",    "data": {      "key_prefix": "mcp_prod_cosmic-1861",      "monthly_request_count": 1000,      "monthly_request_cap": 1000,      "reset_date": "2026-07-01T00:00:00Z"    }  }}
OVERAGE BILLING

Pro and Max users can enable overage billing from Dashboard → Billing. When enabled, requests beyond your monthly limit are metered and charged on your next invoice instead of being blocked.

TierOverage rateBilled
Pro$0.003 per requestAdded to next monthly invoice
Max$0.002 per requestAdded to next monthly invoice

Overage billing can be toggled on or off at any time. When disabled, requests are blocked at the monthly limit. There is no minimum overage charge.

TOP-UP PACKS

Instead of overage billing, you can purchase one-time request packs that add to your monthly balance immediately:

PackExtra requestsPricePer-request rate
Starter2,000$5$0.0025
Growth4,000$10$0.0025

Top-up balances do not expire within the billing month. Unused top-up requests do not roll over to the next month. Purchase from Dashboard → Billing when you hit your limit.

RATE LIMIT HEADERS

Every response includes rate-limit headers so your client can track remaining quota:

text
HTTP/1.1 200 OKX-RateLimit-Limit: 3500X-RateLimit-Remaining: 2847X-RateLimit-Reset: 1717200000X-RateLimit-Burst-Limit: 300X-RateLimit-Burst-Remaining: 298
HeaderMeaning
X-RateLimit-LimitMonthly request cap for your tier
X-RateLimit-RemainingRequests remaining this month
X-RateLimit-ResetUnix timestamp when the monthly counter resets
X-RateLimit-Burst-LimitPer-minute burst cap
X-RateLimit-Burst-RemainingBurst requests remaining in the current window
MONTHLY LIMIT EXCEEDED RESPONSE
json
{  "jsonrpc": "2.0",  "error": {    "code": -32003,    "message": "Monthly usage limit exceeded",    "data": {      "tier": "pro",      "current_usage": 3500,      "limit": 3500,      "reset_date": "2026-07-01T00:00:00Z",      "upgrade_url": "https://zephex.dev/dashboard/billing"    }  }}

When you receive this error, your options are: wait for the monthly reset, purchase a top-up pack, enable overage billing, or upgrade your plan.

USAGE NOTIFICATIONS

Zephex sends email notifications when you approach your limit. Default thresholds are 50%, 75%, and 90%. You can disable or customize these from Dashboard → Settings → Notifications.

  • 50% — informational notice
  • 75% — warning with upgrade suggestion
  • 90% — urgent alert with immediate action options
  • 100% — limit reached, requests blocked (unless overage is enabled)
WEEKLY USAGE DIGEST

Opt into a weekly email summary (sent Mondays at 9am UTC) showing your request count, top tools used, remaining quota, and reset date. Enable from Dashboard → Settings → Notifications → Weekly usage digest.

NEED MORE?

If you need more than 10,000 requests/month or custom rate limits, contact support@zephex.dev to discuss enterprise options.