Pay for the platform. Share only when you save.

SmartGate is the intelligence layer between AI and the world: an MCP-native algorithmic gateway, not an LLM proxy, chatbot, or model router. You keep your host model and connect SmartGate as a tool server. Pricing therefore meters platform access and gateway tool traffic—Research, Context, Memory, Control, and Pipeline—rather than charging as if we hosted the model that reasons and chats.

Plans share one story. Free and Playground exist for individual evaluation with strict fair-use rate limits; bursts soft-fail with HTTP 429, limit_scope, and Retry-After when available. Pro adds a higher monthly token pool, optional L2 hard cap, and a platform fee plus savings share model capped around the published Pro total. Teams raise shared-workspace limits for builders who share one gateway. Enterprise is contract-based with a larger baseline token pool—contact sales rather than reading a public calculator as a quote.

Gainshare is deliberate asymmetry: you pay a platform fee first, and a variable share only after a free savings allowance, using the same internal gateway benchmark the product uses for Est. USD saved. Search-class estimated savings count at a reduced weight toward share; fetch, compress, dedup, pipe, and budget-block savings count fully. Team memory writes and Playground-only estimates stay out of the share tax base. That keeps the bill tied to governed tool traffic, not to a restated vendor LLM invoice.

What counts toward the monthly token pool is tool token_used recorded through budget guard and audit—including compress, fetch, search, and other MCP modules. MCP requests-per-minute per API key is separate from Playground RPM and from the shared smart_search/smart_fetch per-team gateway cap documented under tool limits. Hitting a limit is a soft-fail entitlement signal, not a silent drop: reduce request rate or upgrade for higher limits.

Choose Free to evaluate the seven algorithm primitives on one Streamable HTTP endpoint. Choose Pro when a single team needs Usage Reports, stronger caps, and Gainshare with a published ceiling. Choose Teams when multiple builders share workspace limits and audit. Choose Enterprise when retention, pool size, and contract terms need a sales conversation. In every case SmartGate remains five intelligence capabilities powered by seven primitives—not another AI assistant and not a ChatGPT alternative.

Moving from ad-hoc fetch scripts or per-agent reimplementations usually means pointing MCP clients at one origin, minting team API keys, and turning on Activity Logs before you debate compression ratios. FinOps reviewers should treat Est. USD saved as a gateway counterfactual for comparing tool paths, then reconcile separately against the host model invoice. Security reviewers should start from audit retention by plan and team_id isolation, then sample traces for a pipe that includes search, fetch, dedup, and context_gate.

Pricing pages intentionally avoid invented customer logos, concurrent capacity figures, and fixed savings percentages. Savings depend on input structure and the ratios you set; the dashboard shows per-request metrics from audit. If you need a contractual commitment beyond published Pro and Teams ceilings, use contact sales for Enterprise rather than extrapolating public tiers.