Token Management

Entry, Purpose, and When to Use It

• Entry: after signing in to Routescope, open Token Management in the account center sidebar.
• Purpose: create API Keys, search and filter tokens, review quota, copy secrets, and configure available models, IP restrictions, and expiration.
• Use it when: creating independent credentials for a project, environment, client, or team member.

What Tokens Are For

Tokens are business credentials for calling Routescope API. A typical API call needs:

• the API address from the dashboard,
• the API Key created in token management,
• the model ID copied from the model gallery.

Create separate tokens by project and environment so multiple workloads do not share the same API Key.

Create a Token

1. Open Token Management.
2. Click Add Token.
3. Enter a token name that identifies its purpose.
4. Configure group, quota, available models, IP restrictions, and expiration according to the page fields.
5. Save, then confirm the new token appears in the list.

Search Tokens

1. Find the search box above the token list.
2. Enter a token name or keyword.
3. Check whether the list locates the target token.
4. Clear the search condition to restore the full list.

Filter by Group and Status

1. Find the group filter.
2. Select the target group and review its tokens.
3. Find the status filter and filter enabled or disabled tokens.
4. Filter names and statuses should follow the actual page display.

Check Token Quota

1. Find the target token in the list.
2. Review quota, used quota, or remaining quota fields.
3. If quota is insufficient, edit token quota or create a new token.
4. If quota is normal but calls fail, check model restrictions, IP restrictions, and expiration.

View and Copy the Secret

1. Find the target token in the list.
2. Click the action that shows the full secret.
3. Copy the secret only after confirming the current environment is safe.
4. Store it in server-side environment variables, protected config files, or client authorization settings.

Do not paste full secrets into webpages, screenshots, or public repositories.

Configure Available Models

1. When creating or editing a token, find the available models setting.
2. Select only the models the business needs.
3. Save, then test whether this API Key can call the selected models.
4. If a model call fails, first confirm that the model is allowed by the token.

Configure IP Restrictions

1. When creating or editing a token, find the IP restriction setting.
2. Enter allowed source IP addresses.
3. Save, then test from the corresponding server.
4. If source IP is not fixed, avoid strict restrictions unless required by your security policy.

Configure Expiration

1. When creating or editing a token, find the expiration setting.
2. Set an expiration time for test, demo, or temporary collaboration tokens.
3. Record the expiration date after saving to avoid production interruption.

Enable, Disable, and Delete Tokens

1. Find the target token in the list.
2. Use enable or disable actions to control whether it can be used.
3. Delete a token only after it is no longer used.
4. Before deletion, confirm no online service, script, or client still uses that API Key.

FAQ

Why did I create a token but calls still fail?

Check balance, token status, expiration, model restrictions, and IP restrictions.

How many API Keys should one project create?

Create at least separate keys per environment, such as test and production, so quota limits and troubleshooting are easier.