Vadyl
AI as a native plane

LLM routing

Capability-aware model selection. Tier requirements. Deprecation fallback policy.

This page is the documentation contract for the LLM routing surface in Vadyl's final form. It is not a marketing summary: it names the authorities, projections, runtime behavior, examples, limits, errors, and observability expectations that every product implementation must honor.

What this surface owns

  • LLM routing owns the canonical product-facing contract described here; provider-specific machinery stays behind capability declarations.
  • Capability-aware model selection. Tier requirements. Deprecation fallback policy.
  • The final docs treat this as complete: REST, GraphQL, gRPC, SDK, CLI, MCP, dashboard, observability, limits, errors, and explainability are all covered as projections of one authority.

Canonical authorities

AuthorityRole
AgentManifestCanonical owner for LLM routing; downstream surfaces derive from this rather than inventing their own truth.
AutomationDefinitionCanonical owner for LLM routing; downstream surfaces derive from this rather than inventing their own truth.
PlaneCapabilityGraphPlaces LLM routing inside the UCSA taxonomy and enforces binding, grants, conformance, and consumption.
ILlmModelRouterCanonical owner for LLM routing; downstream surfaces derive from this rather than inventing their own truth.
TokenAccountingPreflightCanonical owner for LLM routing; downstream surfaces derive from this rather than inventing their own truth.

Projection coverage

Surface kindsAgentSkillSurface, AutomationActionSurface, ToolSurface, ModelInferenceAdapter, AnalyticsSurface
Projection facetsAgents, Automations, PlaneCapabilityGraph, Measures, ExposureBindings
ProtocolsRest, OpenApi, Sdk, Cli, Mcp, Dashboard
Public projectionsagent APIs; automation APIs; MCP tools; SDK agents/automation/mcp; CLI agent/automation; dashboard run views

Project-scope parity

    Publish, install, consume

      Consumption evidence

        Runtime behavior

        • agent plan validator
        • LLM capability router
        • MCP projection
        • immutable memory supersession
        • automation compiler

        REST and controller surface

        Code-backed controllers are listed here so the docs menu does not hide the real endpoint surface. The complete route-by-route table remains in the REST controller atlas.

        ControllerBase routeEndpoint countExamples
        Agent/api/Agent1
        POST {agentId}/run
        AgentRun/api/AgentRun6
        GET /
        GET {runId}
        POST {runId}/cancel
        GET {runId}/steps
        AgentPlan/api/AgentPlan10
        GET /
        GET {planId}
        POST /
        POST {planId}/validate
        AgentMemory/api/AgentMemory7
        GET namespaces
        POST namespaces
        GET namespaces/{namespaceId}
        POST apply
        AgentSkill/api/AgentSkill5
        GET /
        GET {id}
        POST /
        PUT {id}
        Automation/api/Automation18
        POST compile
        POST runs/start
        GET runs/{runId}
        GET runs/{runId}/approvals
        KnowledgeCorpus/api/KnowledgeCorpus5
        GET /
        GET {id}
        POST /
        PUT {id}
        AgentModelBinding/api/AgentModelBinding5
        GET /
        GET {id}
        POST /
        PUT {id}
        Connector/api/Connector9
        GET contracts
        GET contracts/{kind}/{majorVersion:int}
        GET implementations
        GET implementations/{implementationId}

        SDK and CLI surface

        ProjectionNamespace / groupCoverage
        SDKagentsdefinitions, runs, plans, memory, skills, model bindings, token accounting, MCP exposure. Rendered methods: 6.
        SDKautomationcompile, definitions, runs, approvals, attempts, signals, compensation. Rendered methods: 6.
        SDKmcptoken issuance, exposure descriptors, tool invocation, resources, prompts. Rendered methods: 6.
        CLIvadyl agentList, inspect, run agents. Rendered commands: 7.
        CLIvadyl automationCompile definitions, manage runs, approvals, attempts, signals, compensation. Rendered commands: 10.
        CLIvadyl connectorContracts, implementations, bindings, builds, conformance, invocation. Rendered commands: 6.

        Input request and output

        POST /api/Agent/{agentId}/run HTTP/1.1
Host: api.vadyl.app
Authorization: Bearer $VADYL_TOKEN
X-Vadyl-Tenant: acme
X-Vadyl-Project: billing
Content-Type: application/json

{
  "surface": "llm-routing",
  "publicationVersion": 412,
  "explain": true
}

        Limits and quotas

          Error model

          ErrorMeaning

          Observability and explainability

            Related references

            Previous
            Full surface atlas
            Next
            Exposure bindings