Track A · research agenda

Route

How do we compose many models and providers behind one reliable interface?

AI-Pass is the infrastructure layer the other tracks plug into.

Directions

  1. Routing as a learned policy over predicted quality, cost, latency, data sensitivity and jurisdiction.
  2. Provider heterogeneity: schema drift, failure modes and silent model updates.
  3. Sovereignty constraints as first-class routing rules with verifiable enforcement.
  4. Measured modularity: cost of adding a provider and overhead versus direct calls.

Picture

ConceptualRouting decisionRequestConstraintsPrivacyJurisdictionCostLatencyPolicyProvider
View as table
Routing flow
Stage
Request
Constraints
Policy engine
Provider

Planned metrics

Values stay Pending until we publish logs.

Routing regret

Gap versus an oracle routing policy on the same request set.

Value: Pending

Cost per request

Monetary cost of a routed request, including fallbacks.

Value: Pending

Latency overhead

Added latency versus a direct provider call.

Value: Pending

Policy-violation rate

Share of requests that break a stated routing rule.

Value: Pending

Time to onboard a provider

Elapsed time from contract to first routed request.

Value: Pending

Connects to

Ground · Assure · Foundation · Physical