Agent Studio, Model Routing & MCP Governance

The isA Console serves as the unified operational cockpit for enterprise agent orchestration, model routing gateways, and distributed MCP tool cluster governance. This chapter guides developers and architects through the live configuration and execution lifecycle.

Console Operations (53s)

Console Deep Dive: Orchestrate Agents, Route Models & Audit MCP

Launch Console Dashboard

Jump to Key Action

Real-world engineering walkthrough inside the isA Platform Enterprise Workspace: inspecting the 100M Token credit pool, configuring Agents in Agent Studio, routing between Claude 3.7 / GPT-4o / Local models, exploring the 321 published MCP tool cluster, analyzing real-time trace telemetry, and issuing scoped RBAC API keys.

1. Architectural Highlights Demonstrated

1.1 Dual-Token Authentication & Enterprise Isolation

The walkthrough operates under the authentic demo@isagent.io session within the isA Platform organization (org_cdb4c4cf7e2c). Enterprise isolation guarantees:

Zero Cross-Tenant Leakage: Model provider configurations, private prompt sets, and execution memory remain strictly partitioned.
Unified Credit Economics: Real-time metering tracks input/output tokens, cache read hits, and reasoning effort against the allocated 100M quota.

1.2 Model Gateway & Failover Matrix

In dashboard/models, architects configure fine-grained routing policies:


routing_policy:
  primary: "claude-3-7-sonnet"
  fallback: "gpt-4o"
  circuit_breaker:
    consecutive_failures: 3
    timeout_seconds: 15
  rate_limits:
    tpm: 2000000
    rpm: 5000

1.3 321 Published MCP Tools

In dashboard/mcp, the system surfaces the complete Model Context Protocol ecosystem:

System Integrations: SQL Database connectors, MinIO object storage, Git repo synchronizers.
Automation Providers: UiPath RPA automation triggers, Feishu/Lark webhooks, Slack alerts.
Contract Verification: Every tool invocation validates the JSON Schema payload and passes cryptographic attribution signatures.