Merge Landing Page

GLM 4.7:
Everything you need to know about the model

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

GLM 4.7 pricing

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

Test GLM 4.7 with Merge Gateway’s Simulator

GLM 4.7

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 GLM 4.7 with Merge Gateway

Merge Gateway is a unified LLM API that lets your product route requests to GLM 4.7 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 4 Turbo 2024 04 09

Gpt 5

Gpt 5.1

Gpt 5.1 2025 11 13

Gpt 5.1 Chat Latest

Gpt 5.2

Gpt 5 2025 08 07

Gpt 5.2 2025 12 11

Gpt 5.2 Chat Latest

Gpt 5.3 Chat Latest

Gpt 5.4

Gpt 5.4 2026 03 05

Gpt 5.4 Mini

Gpt 5.4 Mini 2026 03 17

Gpt 5.4 Nano

Gpt 5.4 Nano 2026 03 17

GPT-5.5

Gpt 5.5 2026 04 23

Gpt 5 Chat Latest

Gpt 5 Mini

Gpt 5 Mini 2025 08 07

Gpt 5 Nano

Gpt 5 Nano 2025 08 07

Gpt 5 Search Api

GLM 4.7 FAQ

In case you have any more questions on using GLM 4.7, we’ve addressed several below.

Heading

What provider owns GLM 4.7?

GLM 4.7 is a Amazon Bedrock model.

Which vendors can run GLM 4.7?

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

What context window does GLM 4.7 support?

GLM 4.7 supports 200,000 tokens on the primary listed vendor route.

What capabilities does GLM 4.7 support?

Gateway currently lists streaming support for GLM 4.7 across its available vendor routes.

Try GLM 4.7 through Merge Gateway

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

Start building for free

Get a demo