Pro & Max Guide

This page covers what changes on Pro and Max tiers: team setup, key scopes, request management, and support.

What Pro unlocks beyond Free

Unlimited API keys so you can create one key per developer, project, environment, or workflow.
Custom key scopes so each key can be restricted to a subset of tools.
10 backends for broader infrastructure coverage.
777 bonus requests for your first 7 days (during the free trial).

WHAT'S DIFFERENT ON MAX

10,000 requests/month for larger teams and automated workflows.
20 backends for larger infrastructure setups.
Priority support with fastest queue placement through the feedback flow.

CUSTOM KEY SCOPES

On Pro and Max, API keys can be restricted to specific tools. Calls outside the allowed scope return 403 Forbidden.

# CI/CD pipeline key — only security scanningAllowed tools: audit_headers, Zephex_dev_info, find_code # Junior developer key — no architecture analysisAllowed tools: get_project_context, read_code, find_code # Full access key — all toolsAllowed tools: (leave blank for full access)

Scopes are set during key creation and can be updated from the dashboard later.

TEAM SETUP

Create one key per developer such as alice-dev.
Create environment keys such as team-staging.
Restrict CI keys to security tools when possible.
Use Dashboard → Usage to monitor request counts by key.
Revoke a compromised key individually instead of rotating the whole team.

REQUEST MANAGEMENT

Call scope_task first to cut 3 to 8 unnecessary reads.
Cache get_project_context output in session notes.
Use find_code before read_code.
Run audit_headers after deploy, not repeatedly during development.

PRIORITY SUPPORT

Max support goes to the top of the queue. Use the feedback form at /feedback with your account email and MAX in the subject. Target response time is within 24 hours on business days.