Merge Landing Page

Gemma 3 12B:
Everything you need to know about the model

Gemma 3 12B is a Amazon Bedrock model available through Merge Gateway via Amazon Bedrock. Use it with Gateway routing policies, spend controls, request logs, and a 128,000 token context window. It supports streaming through at least one Gateway vendor route.

Gemma 3 12B pricing

| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention | | --- | ---: | ---: | --- | | Amazon Bedrock | $0.0900 | $0.2900 | Yes |

Test Gemma 3 12B with Merge Gateway’s Simulator

Gemma 3 12B

Model

System prompt

Synced

User message

Synced

Response

Run simulation to see response

Cost

—

Tokens

—

Latency

—

Ready to try it out?

Start routing requests to hundreds of large language models in your product within minutes.

Start building for free

Get a demo

Route requests to Gemma 3 12B with Merge Gateway

Merge Gateway is a unified LLM API that lets your product route requests to Gemma 3 12B and every other major model through a single endpoint. You get built-in fallback routing, per-request cost tracking, zero data retention support, and observability without changing your application architecture.

To get started in seconds, add our Gateway Implementation skill to your project, or pick your preferred SDK below. Check out our other quick start skills here.

Install the Merge Gateway SDK

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Make your first API call

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Try a diffrent model

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Install the Merge Gateway SDK

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Make your first API call

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Try a diffrent model

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Install the Merge Gateway SDK

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Make your first API call

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Try a diffrent model

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Install the Merge Gateway SDK

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Make your first API call

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Try a diffrent model

Python

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Explore other models available in Merge Gateway

Gpt 5 Search Api 2025 10 14

Grok 3

Grok 3 Mini

Grok 4 0709

Grok 4 1 Fast Non Reasoning

Grok 4 1 Fast Reasoning

Grok 4.20

Grok 4.3

Grok 4 Fast Non Reasoning

Grok 4 Fast Reasoning

Grok Code Fast 1

Jamba 1.5 Large

Jamba 1.5 Mini

Kimi K2 0711 Preview

Kimi K2 0905 Preview

Kimi K2.5

Kimi K2.6

Kimi K2 Thinking

Kimi K2 Thinking Turbo

Kimi K2 Turbo Preview

Llama 3.1 70B

Llama 3.1 8B

Llama 3.2 11B

Gemma 3 12B FAQ

In case you have any more questions on using Gemma 3 12B, we’ve addressed several below.

Heading

What provider owns Gemma 3 12B?

Gemma 3 12B is a Amazon Bedrock model.

Which vendors can run Gemma 3 12B?

Amazon Bedrock is the default listed vendor, and other active vendors may also be available.

What context window does Gemma 3 12B support?

Gemma 3 12B supports 128,000 tokens on the primary listed vendor route.

What capabilities does Gemma 3 12B support?

Gateway currently lists streaming support for Gemma 3 12B across its available vendor routes.

Try Gemma 3 12B through Merge Gateway

Route, observe, and control AI requests across providers from one API.

Start building for free

Get a demo