Quick Start

Entry, Purpose, and When to Use It

• Entry: in the documentation sidebar, open Learn the Console, then Quick Start. The actual operation starts from the account center after you sign in to Routescope.
• Purpose: turn the first integration into executable steps, from account checks to the first API call and billing audit.
• Use it when: you are integrating Routescope API for the first time, validating a new model, or creating an isolated API Key for a new project.

Check the Dashboard

1. Sign in to Routescope and enter the account center.
2. Open Dashboard in the left navigation.
3. Confirm that Current Balance is enough for testing.
4. Review model consumption data, date statistics, and common API addresses.
5. If you need the base endpoint, copy it from the page.

If balance is insufficient, top up first and then continue.

Top Up

1. Open Top Up Balance from the left navigation.
2. Check your current balance.
3. Enter a top-up amount. The credited quota is denominated in USD.
4. Review the credited quota shown on the page.
5. If packages, promo codes, or payment methods are available, choose the options you need.
6. After payment, return to the page and confirm that the balance has been credited.

Choose a Model

1. Open Model Gallery.
2. Search by model name or keyword.
3. Filter by provider, token group, billing type, tags, or endpoint type.
4. Review pricing and confirm the input, output, or task billing path.
5. In card view or table view, find the target model and copy its model ID.

The model ID is the standard identifier you will use in playground tests and API calls.

Test the Model

1. Open Playground.
2. Enter Text Conversation.
3. Select the model you confirmed.
4. If you need visual input, fill in the image URL field shown on the page.
5. Configure visible parameters such as max tokens and random seed.
6. Send a test message.
7. Review the response and debug information to confirm model behavior, latency, and error messages.

Create an API Key

1. Open Token Management.
2. Click Add Token.
3. Enter a token name. Use a project or environment name such as web-prod or agent-test.
4. Configure allowed models, quota, IP restrictions, and expiration as needed.
5. Save, then view and copy the full secret.

Keep the full secret in server-side environment variables or protected client configuration. Do not publish it.

Make an API Call

1. Prepare three values: the API address from the dashboard, the API Key from token management, and the model ID from the model gallery.
2. Open the API reference and choose the capability page you need.
3. Follow the example request and put the endpoint, API Key, and model ID into your code, script, or client configuration.
4. Send a minimal test request to confirm authentication, model permission, and balance.
5. For detailed field descriptions, continue to the matching API reference. This console guide only explains the integration flow.

Review Results and Billing

1. Open Operation Records.
2. In Usage Logs, search by date, token name, model name, group, or request ID.
3. Review input, output, cost, RPM, TPM, and request details.
4. For async image, audio, or video tasks, switch to Task Logs to check task status, result, or failure reason.
5. For financial reconciliation, open Billing and Invoices to review billing records, order status, and consumption records.

FAQ

Why can I not call the API after creating a key?

Check balance first, then confirm that the token is enabled, not expired, and not restricted away from the current model or source IP.

Should I write code first or test the model first?

Test the model in Playground > Text Conversation first, then use the same model ID and access settings in your code.