Merge Landing Page

Llama 3.2 90B:
Everything you need to know about the model

Llama 3.2 90B is a Meta 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.

Llama 3.2 90B pricing

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

Test Llama 3.2 90B with Merge Gateway’s Simulator

Llama 3.2 90B

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 Llama 3.2 90B with Merge Gateway

Merge Gateway is a unified LLM API that lets your product route requests to Llama 3.2 90B 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

Gemini 3.1 Pro Preview

Gemini 3.1 Pro Preview Customtools

Gemini 3.5 Flash

Gemini 3 Flash Preview

Gemini 3 Pro Preview

Gemini Flash Latest

Gemini Flash Lite Latest

Gemini Pro Latest

Gemma 3 12B

Gemma 3 27B

Gemma 3 4B

GLM-4-32B-0414-128K

GLM-4.5

GLM-4.5-Air

GLM-4.5-AirX

GLM-4.5-X

GLM-4.6

Glm47

GLM 4.7

GLM 4.7 Flash

GLM-4.7-FlashX

Glm 5

GLM-5

GLM-5-Turbo

Llama 3.2 90B FAQ

In case you have any more questions on using Llama 3.2 90B, we’ve addressed several below.

Heading

What provider owns Llama 3.2 90B?

Llama 3.2 90B is a Meta model.

Which vendors can run Llama 3.2 90B?

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

What context window does Llama 3.2 90B support?

Llama 3.2 90B supports 128,000 tokens on the primary listed vendor route.

What capabilities does Llama 3.2 90B support?

Gateway currently lists streaming support for Llama 3.2 90B across its available vendor routes.

Try Llama 3.2 90B through Merge Gateway

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

Start building for free

Get a demo