メインコンテンツへスキップ
更新日: 2026-06-06
Coze is ByteDance’s bot and workflow platform. It is useful for building bots, chaining workflow steps, calling plugins, and publishing to different channels. When connecting Coze to Crazyrouter, the most stable and public-doc-friendly path is not to assume every Coze plan supports direct custom-model integration. The recommended public path is to use an HTTP / API plugin or a workflow HTTP request node first.

​
Start Here

For most Crazyrouter users, these are the two recommended Coze integration paths:
  • Option 1: call Crazyrouter through a Create from API plugin
  • Option 2: call Crazyrouter through a workflow HTTP request node
Do not present “attach Crazyrouter directly as a custom model in Coze model management” as the default public guide, because:
  • Coze features differ across editions, regions, and plans
  • Coze’s published plan FAQ explicitly lists custom model as an enterprise flagship capability
  • For public documentation, the safer baseline is the HTTP / API plugin route
The most important accuracy rule for this page is: document Coze’s public baseline as “call Crazyrouter through HTTP / API plugins or workflow HTTP requests”, not “every user can directly mount a custom upstream model”.

​
Who This Guide Is For

  • Users who want to call Crazyrouter inside a Coze bot or workflow
  • Users who want Crazyrouter to act as an external model endpoint
  • Users who want the smallest reproducible setup before touching enterprise-only capabilities
  • Teams that want plugin- or workflow-based access to multiple models

​
Public baseline: HTTP / API plugin route

Recommended parameters:
  • Request method: POST
  • URL: https://api.crazyrouter.com/v1/chat/completions
  • Headers:
    • Authorization: Bearer sk-xxx
    • Content-Type: application/json
  • First validation model: gpt-5.5

​
Why this route comes first

Because it:
  • depends less on Coze plan differences
  • makes it easier to tell whether the issue is Coze setup or Crazyrouter token / model scope
  • is the most stable route to document publicly

​
Requirements And Prerequisites

Suggested initial allowlist:
  • gpt-5.5
  • claude-opus-4-8
  • gemini-3.1-pro

​
Option 1: Connect Crazyrouter Through An API Plugin

1

Step 1: Create a dedicated Crazyrouter token for Coze

For the first pass, only allow:
  • gpt-5.5
  • claude-opus-4-8
Do not enable too many models on day one. Troubleshooting is easier when the scope is small.
2

Step 2: Create an API plugin in Coze

In the Coze workspace, open the area that matches your current version, usually something like:
  • Plugins
  • Create Plugin
  • Create from API or a similarly named entry
Exact menu names may vary by Coze version, region, or product line, but the core idea is the same: create a plugin that calls an external HTTP API.
3

Step 3: Set the request method and URL

Enter:
  • Method: POST
  • URL: https://api.crazyrouter.com/v1/chat/completions
4

Step 4: Configure headers

Enter:
5

Step 5: Start with the smallest request body

For the first test, use:
If your plugin UI supports parameter mapping, map user input into a placeholder such as {{input}}.
6

Step 6: Validate the plugin connection first

If your version supports plugin debugging, send:
Make sure the API returns successfully before attaching the plugin to a bot or workflow.
7

Step 7: Add the plugin to a bot or workflow

After the plugin passes standalone testing, attach it to:
  • a bot plugin capability
  • or a workflow node
For the first rollout, keep the task simple, such as summarization, rewrite, or a fixed Q&A step.

​
Option 2: Connect Crazyrouter Through A Workflow HTTP Request Node

If you do not want to maintain a separate plugin, you can call Crazyrouter directly from a workflow HTTP request node.
  • Request method: POST
  • URL: https://api.crazyrouter.com/v1/chat/completions
  • Headers:
    • Authorization: Bearer sk-xxx
    • Content-Type: application/json
  • Body:
  1. Send a fixed string such as Reply only OK
  2. Replace the fixed string with a variable input
  3. Map the result into downstream nodes only after the HTTP node is stable

​
How To Think About “Custom Model Integration”

Some Coze versions or plans may support custom-model integration, but that should not be the default public Crazyrouter guide. Reasons:
  • Coze’s own plan FAQ currently lists custom model as an enterprise flagship capability
  • For most ordinary users, the most reproducible and lowest-friction route is still HTTP / API plugins
  • This page therefore treats custom-model support as background context, not as the default public setup path

​
Token Best Practices

​
Validation Checklist

  • Created a dedicated Crazyrouter token for Coze
  • Chosen the HTTP / API plugin route or workflow HTTP request route first
  • Set the request URL to https://api.crazyrouter.com/v1/chat/completions
  • Filled the Authorization header as Bearer sk-xxx
  • Set Content-Type to application/json
  • Validated the smallest request body with gpt-5.5
  • Confirmed the plugin or HTTP node works in standalone debugging
  • Confirmed it still works after attaching to the bot or workflow
  • Confirmed the request appears in Crazyrouter logs

​
Common Errors And Fixes

​
FAQ

​
What is the best Coze-to-Crazyrouter route?

In public docs, prefer the HTTP / API plugin route or the workflow HTTP request node route.

​
Why is “custom model integration” not the main path here?

Because Coze capabilities vary a lot by version and plan, and Coze’s plan FAQ also places custom model under enterprise flagship capabilities. Public docs should lead with the most reproducible lower-threshold HTTP path.

​
What URL should I enter?

Use https://api.crazyrouter.com/v1/chat/completions.

​
What should the first model be?

Start with gpt-5.5.

​
When should I add Claude or more models?

Only after the single-model, single-node, single-task path is already stable.
If your goal is “make Coze call Crazyrouter reliably first”, the most important thing is not choosing the fanciest integration path. It is getting the smallest HTTP / API flow working end to end.