Skip to main content
ROUTER decision routing is Aria Compute’s unified inference-gateway product. A set of decision layers routes each request: semantic (YAML v0.3) handles chat routing, the lightweight agent runs an in-process tool loop, and afm-d calls System One Choice through aria-engine. Each request then forwards to shared providers under hard constraints. One request uses exactly one layer. The gateway data plane implements the standard OpenAI /v1/chat/completions and /v1/models endpoints, so existing SDKs work unchanged.

Decision layers

ROUTER routes requests across several parallel decision layers. The routing result (layer, decision, model) comes back in response headers:

Routing config (YAML v0.3)

You declare entrypoints, providers, and routing rules in a YAML v0.3 config that ROUTER reloads dynamically. The config blocks:

Gold entrypoints

Common virtual entrypoints ship with built-in recipes:
  • ariacompute/semantic-auto
  • ariacompute/agent-auto
  • ariacompute/afm-d-auto
The afm-d layer needs AFM_ENGINE_URL pointing at a running aria-engine. The layer and decision come back in x-aria-router-* response headers.

Constraints and governance

Shared provider models and hard constraints (cost, latency, capability) are evaluated at request time. The management plane covers authentication, routing configuration, cost tracking, and key management under /v1/router/*; AFM_ENGINE_URL can wire afm-d into System One.

How to run

See also