Merge Landing Page

meta-llama/Llama-3.3-70B-Instruct-Turbo:
Everything you need to know about the model

meta-llama/Llama-3.3-70B-Instruct-Turbo is a Meta model available through Merge Gateway via Amazon Bedrock. Use it with Gateway routing policies, spend controls, request logs, and a 131,072 token context window. It supports streaming through at least one Gateway vendor route.

meta-llama/Llama-3.3-70B-Instruct-Turbo pricing

| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention | | --- | ---: | ---: | --- | | Amazon Bedrock | $0.7200 | $0.7200 | Yes | | Together AI | $0.8800 | $0.8800 | No |

Test meta-llama/Llama-3.3-70B-Instruct-Turbo with Merge Gateway’s Simulator

meta-llama/Llama-3.3-70B-Instruct-Turbo

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 meta-llama/Llama-3.3-70B-Instruct-Turbo with Merge Gateway

Merge Gateway is a unified LLM API that lets your product route requests to meta-llama/Llama-3.3-70B-Instruct-Turbo 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

Openai.Gpt Oss Safeguard 20B

Open Mistral Nemo 2407

palmyra-x4

palmyra-x5

Pixtral Large 2411

Pixtral Large Latest

Qwen25 Vl 72B Instruct

Qwen3 235B

Qwen3 32B

Qwen35 397B A17B

Qwen3.6 Plus

Qwen3 Coder 30B

Qwen 3 Next 80B Instruct

Qwen3P5 35B A3B

Qwen3Vl 8B Instruct

Qwen/Qwen2.5-VL-72B-Instruct

Qwen/Qwen3-235B-A22B-Instruct-2507-tput

Qwen/Qwen3.5-35B-A3B

Qwen/Qwen3.5-397B-A17B

Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8

Qwen/Qwen3-Coder-Next

Qwen.Qwen3 Next 80B A3B

Qwen/Qwen3-Next-80B-A3B-Instruct

Qwen.Qwen3 Vl 235B A22B

meta-llama/Llama-3.3-70B-Instruct-Turbo FAQ

In case you have any more questions on using meta-llama/Llama-3.3-70B-Instruct-Turbo, we’ve addressed several below.

Heading

What provider owns meta-llama/Llama-3.3-70B-Instruct-Turbo?

meta-llama/Llama-3.3-70B-Instruct-Turbo is a Meta model.

Which vendors can run meta-llama/Llama-3.3-70B-Instruct-Turbo?

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

What context window does meta-llama/Llama-3.3-70B-Instruct-Turbo support?

meta-llama/Llama-3.3-70B-Instruct-Turbo supports 131,072 tokens on the primary listed vendor route.

What capabilities does meta-llama/Llama-3.3-70B-Instruct-Turbo support?

Gateway currently lists streaming support for meta-llama/Llama-3.3-70B-Instruct-Turbo across its available vendor routes.

Try meta-llama/Llama-3.3-70B-Instruct-Turbo through Merge Gateway

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

Start building for free

Get a demo