FinAssistCommand Center
DAassociate
Runtime signals
CPU utilisation
46.0%
GPU pool 38.0% · 12 vCPU
Memory footprint
64.0%
30.7 GB of 48 GB resident
Token consumption
18.4k
tokens / min · $41.72 spent this hour
Inference latency p50
720 ms
p95 720 ms · budget 2,500 ms
Per-agent runtime
AgentCPUMemoryLatency p50 / p95Tokens in / outReq/sErrors
Core Case Router
46%
62%
640 ms / 1480 ms5.1k / 8408.40.30%
Fraud Agent
58%
71%
910 ms / 2240 ms3.5k / 6105.10.60%
Account Agent
31%
44%
380 ms / 820 ms1.9k / 31011.20.20%
Knowledge Agent
63%
78%
1120 ms / 2680 ms6.2k / 7203.71.10%
Compliance Agent
27%
39%
520 ms / 1180 ms2.3k / 3904.40.10%
Model version tracking
AgentModelVersionServing tierContextPromoted
Core Case Routerfinassist-orchestrator
v4.2.1active
Gateway · frontier-tier200k12 Sep 2026
Fraud Agentfinassist-fraud
v3.8.0active
Gateway · reasoning-tier128k04 Sep 2026
Account Agentfinassist-account
v3.5.2active
Gateway · fast-tier128k28 Aug 2026
Knowledge Agentfinassist-knowledge
v2.9.4-rc2canary
Gateway · reasoning-tier200k19 Sep 2026
Compliance Agentfinassist-compliance
v3.1.0active
Gateway · reasoning-tier128k22 Aug 2026
Knowledge Agentfinassist-knowledge
v2.8.7deprecated
Gateway · reasoning-tier128k02 Aug 2026

Telemetry is sampled every 2 seconds across the orchestration pool. Latency budgets and error-rate ceilings feed the same guardrails used by the failure-mode suite — a sustained p95 above 2,500 ms trips the circuit breaker and routes work to cached fallbacks.

9:41
Customer view
Marcus Whitfield
Case updatesIntake
FinAssist Bank
We received your dispute. Case #CS-48291. We'll text you with updates.
Today 10:42 AM
FinAssist Bank · secure messaging