Dashboard

The MultiRoute dashboard at https://multiroute.ai gives you a visual overview of your projects, keys, traffic, and routing behavior.

Use the dashboard to:

• Create and manage projects/spaces
• Issue and revoke API keys
• Inspect logs and metrics
• Configure routing rules and model priorities

Projects and Spaces

A project (sometimes referred to as a space) represents a logical environment, such as a product, team, or deployment stage (e.g. development, staging, production).

Within a project you can:

• View project overview: Recent traffic, error rate, and top models used.
• Manage environments: Separate keys and routing rules per environment where needed.
• Invite collaborators (in progress): Team-level access controls and roles are planned but may not be fully available yet.

When in doubt, create one project per application or service that talks to MultiRoute.

API Keys

The API Keys section lets you create and manage credentials for accessing the /v1 API.

Typical actions:

• Create keys for each application, environment, or service.
• Label keys to indicate their purpose (e.g. “web-backend-prod”, “batch-jobs-dev”).
• Rotate keys periodically by creating a new key, updating your application, and then revoking the old key.
• Revoke keys immediately if they are no longer needed or suspected to be compromised.

Keys are always scoped to a project, and rate limits and usage metrics are generally tracked per key and per project.

Logs and Metrics

The Logs or Observability section (naming may evolve while this feature is in beta) provides:

• Request logs: High-level records of incoming requests and responses.
• Latency metrics: p50, p95, p99 latencies across providers and models.
• Error metrics: Error counts and rates grouped by provider, model, and error type.

These views help you answer questions such as:

• Which models are contributing most to latency?
• Are errors spiking for a particular provider?
• How has traffic changed over time?

For more detail on how to use these tools, see Logs and Metrics.

Routing Configuration

The Routing or Config section is where you manage how MultiRoute sends requests to underlying models and providers.

From the dashboard you can:

• Define routing rules for different use cases or products.
• Set model priorities (e.g. preferred primary model, fallbacks).
• Configure timeouts and failure behavior.
• Preview and validate current configuration before deploying changes.

Routing changes made via the UI are reflected in the same configuration that backs the /v1/config API. You can think of the dashboard as a human-friendly editor for the same concepts that the API exposes.

Activity and Audit Trail (In Progress)

The dashboard is designed to provide an audit trail of key changes, such as:

• Who created, rotated, or revoked an API key.
• Who modified routing rules or project-level settings.

This activity timeline is in progress and may not yet surface all events, but the intent is to give teams a clear history for debugging and compliance.