VeriSwarm
About
Suite
Gate — Trust ScoringGuard — SecurityPassport — IdentityVault — AuditAgent Runtime & RouterManaged AgentsIntegrations
DocsAgent Skill
LoginRegister
  1. Home
  2. /Docs
  3. /Agent runtime
VeriSwarm
AboutTrust CenterDocsAPIInvestorsAgent SkillOATS SpecBlogTermsPrivacy

Getting Started

IntroductionUser GuideIntegration Guide

Platform

GateGuardPassportVaultAgent RuntimeManaged AgentsPortable Credentials

Integration

Agent IntegrationsPython SDKNode.js SDKMCP ServerWebhook Security

Enterprise

SSO Configuration

Technical Reference

API ReferenceArchitectureData Model

Legal

Terms of ServicePrivacy Policy

Agent Runtime & Router

VeriSwarm now includes an execution pillar alongside trust, security, identity, and audit.

What it does

The Agent Runtime & Router decides how agent work should run once trust has been established. It provides:

  • complexity-aware routing between simple and complex execution paths
  • health tracking and cooldown behavior for unstable providers or runtimes
  • fallback chains when a preferred execution path becomes unavailable
  • Guard-aware execution so policy interception remains active during runtime operations

Why it matters

Trust without execution control is incomplete. Platforms need to know not only whether an agent should act, but also how that action should be executed safely and reliably.

Typical use cases

  • route lightweight tasks to low-cost execution paths
  • escalate complex workflows to stronger runtimes
  • prevent repeated failure loops from unhealthy providers
  • preserve consistent runtime behavior across fleets of deployed agents

Relationship to the other pillars

  • Gate decides whether the agent should be allowed to act
  • Guard constrains what the runtime can safely do
  • Passport proves who the agent is and what scopes it holds
  • Vault records what happened during execution
  • Managed Agents packages the runtime into an operator-friendly service