Merge Gateway Adds Granular AI Budgets
Merge Gateway now documents spend controls across organizations, projects, API keys, and customers. Soft limits alert without blocking, while hard limits reject subsequent requests with HTTP 402.
Granular budgets are essential once AI usage becomes production infrastructure, and Merge’s pre-provider enforcement makes blocked requests costless. The operational caveat is that the request crossing a limit still completes, while budget changes can take up to an hour to apply.
- –Organization credit acts as a backstop across all Gateway traffic.
- –Project and per-key limits isolate spend by workload, team, credential, or environment.
- –Customer budgets support products reselling Gateway through Embedded Routing.
- –Remaining-budget headers enable applications to display or react to spend thresholds.
- –Project budgets require a scoped project key or X-Project-Id header; a body-only project_id does not enforce them.
DISCOVERED
1h ago
2026-10-06
PUBLISHED
1h ago
2026-10-06
RELEVANCE
AUTHOR
shensi