Playground

Entry, Purpose, and When to Use It

• Entry: after signing in to Routescope, open Playground, then enter Text Conversation.
• Purpose: test models online, configure model, image URL, max tokens, random seed, and other parameters, send messages, and inspect debugging information.
• Use it when: validating model behavior before coding, troubleshooting model configuration, testing prompts, or trying multi-turn messages.

Enter Text Conversation

1. Open Playground.
2. Select Text Conversation.
3. Confirm that the message input, model configuration, and debug information areas are loaded.

If page entry or layout changes, follow the actual page display.

Configure the Model

1. Choose the target model in the model selector.
2. If group, provider, or model search fields are available, use them to locate the model.
3. Confirm that the model ID matches the ID copied from Model Gallery.
4. If the model is unavailable, check account balance, token group, or model permission.

Configure Image URL

1. If the selected model supports image input, find the image URL field.
2. Enter an accessible image URL.
3. Before sending, confirm the image URL can be accessed by the platform.
4. If no image URL field appears, the current model or mode may not support it.

Configure Max Tokens

1. Find the max tokens setting.
2. Enter the maximum tokens allowed for this response.
3. For availability tests, start with a smaller value.
4. For long output, increase the value based on the task.

Configure Random Seed

1. Find the random seed setting.
2. Enter a fixed seed to make similar outputs easier to reproduce.
3. If reproducibility is not needed, leave it blank or use the page default.

Whether seed takes effect depends on model capability and page support.

Send Messages

1. Enter test content in the message box.
2. Click send.
3. Wait for the model response.
4. If the request fails, review page error prompts and debug information.

Switch Message Roles

1. Find the role selector in the message editor.
2. Choose roles such as system, user, or assistant according to the page display.
3. Adjust message order or content, then send again.

Role switching is useful for testing system prompts, multi-turn context, and the influence of assistant replies on later output.

Inspect Debug Information

1. After sending a message, open the debug information area.
2. Review request content, response content, errors, or timing information.
3. If the result is abnormal, check model, parameters, image URL, and message roles first.
4. For field-level details, jump to the matching API reference.

Retry, Copy, Edit, and Delete Messages

1. Find retry, copy, edit, or delete actions in message bubbles or action menus.
2. Use retry to regenerate a response.
3. Use copy to keep results or prompts.
4. Use edit to adjust a message and send again.
5. Use delete to remove irrelevant messages and reduce context noise.

Import and Export Debug Configuration

1. Find the import or export configuration entry.
2. Export current model, parameter, and message settings so the team can reproduce them.
3. After importing an existing configuration, check whether model and parameters are still available.
4. If import fails, follow the page prompt to check file format.

FAQ

Why are some parameters not displayed?

Different models support different capabilities. Whether image URL, random seed, or other parameters appear depends on the current model and page support.

Why does playground succeed but code fails?

Check whether the Base URL, API Key, and model ID in your code match the playground test, then inspect request details in Operation Records.