Google adds two Gemini API tiers for UK teams

What Google announced this week

On Wednesday 2 April 2026, Google announced two new service tiers for the Gemini API: Flex and Priority. UK businesses building AI-powered workflows now have a direct way to manage cost and reliability in a single API setup.

What changed

The Gemini API previously offered a single processing approach. Google has now split that into two distinct tiers, each suited to a different type of task.

The Flex tier is designed for background tasks that can tolerate some delay. Think CRM updates, data enrichment, document processing, and overnight batch jobs. It cuts processing costs by 50% compared to the standard rate.

The Priority tier is built for real-time, user-facing applications. Customer support bots, live assistants, and any tool where a user is waiting for a response belong here. Priority processing offers higher reliability during peak usage. Both tiers are accessible through the same standard synchronous endpoints, so no architectural overhaul is needed to adopt them.

Why it matters for business professionals

For IT managers overseeing AI infrastructure, this update changes the cost calculation significantly. Background tasks that previously consumed the same budget as live customer interactions can now run at half the cost. That saving compounds quickly across high-volume workflows.

Automation engineers building integrations with tools like n8n or Zapier can now route tasks by urgency. Non-critical jobs go to Flex. Time-sensitive jobs go to Priority. This removes the manual decision-making that previously required either custom logic or accepting a flat cost structure.

UK SMEs can use this update to lower operational costs for non-critical tasks such as CRM updates and data enrichment, while keeping customer-facing AI reliable without complex changes to existing setups. For teams already running Gemini API workflows, this is a meaningful reduction in monthly spend with no rebuild required.

Practical applications

Here are three actions IT managers and automation engineers can take within five working days.

1. Audit your current Gemini API usage and separate tasks into two lists: those where a user is waiting for a response, and those running in the background. This audit takes under 30 minutes with access to your API logs.

2. Update your workflow configuration in n8n, Zapier, or your integration layer to route background tasks to the Flex tier. Start with one workflow, such as a nightly CRM sync or a batch data enrichment job, before rolling out across all processes.

3. Assign your customer-facing AI tools, such as support bots or real-time query handlers, to the Priority tier. This protects uptime during peak periods without changing the underlying model or prompt configuration.

Considerations and limitations

The Flex tier is not suitable for any workflow where response speed affects the user experience. Applying it to live-facing tools will introduce noticeable delays.

Pricing details beyond the 50% reduction for Flex are not confirmed in Google's announcement. IT managers should review current API billing statements before projecting savings.

Availability may vary by region or account type. Teams on managed Google Cloud contracts should confirm tier access with their account contact before building new routing logic.

Next step

If your team is running AI workflows and wants to reduce costs without rebuilding your setup, now is the right time to act. gecco works with UK SMEs to identify where Flex and Priority routing can reduce spend and improve reliability across automation workflows. Book an automation consultation to explore how this fits your current setup.