arthai-marketplace

/router

Operate the Arth Router — the live routing decision service: status, usage summary, pool calibration, override reporting.

Synopsis

/router <status|summary|pools|calibrate|outcome DECISION_ID>

When to use it

• Checking whether the router is up and what it’s routing (status, pools)
• The weekly validation check-in: override rate and cost-estimate bias (summary)
• Calibrating your subscription window capacity after hitting a rate limit (calibrate)
• Reporting the actual cost/tokens of a routed task, or recording that you overrode a decision (outcome)
• Not for: installing the router — that’s /router-setup

Quickstart

/router summary

What you’ll see: decisions/denials/outcomes counts, total spend, each capacity pool’s state (headroom / on_pace / tight / exhausted) with its rationale, and the two kill-test numbers called out — override rate (> 0.5 means the routing rules are wrong) and estimate bias (> 10% means the cost model needs fixing).

Examples

/router status                    # health: version, catalog sizes, pools, auth/audit
/router summary                   # the weekly validation digest
/router pools                     # capacity pools with burn state + rationale
/router calibrate                 # guided window-capacity calibration
/router outcome rd_ab12cd34ef     # report actuals for a routed decision

What it does

1. Reads ARTH_ROUTER_URL from the environment (set by /router-setup).
2. Calls the corresponding router API (/health, /usage/summary, /policy/pools, /outcome) and presents the JSON as a readable digest.
3. For calibrate, walks the capacity-estimate correction: rate-limited while the pool showed well under 100% → lower capacity_usd; never limited at 100% → raise it.
4. If the router is unreachable, says so — the triage hook is falling back to the static routing table, which is the designed behavior, not an outage.

Requirements

• A running Arth Router (/router-setup) and ARTH_ROUTER_URL in the environment.

Output

A readable digest of the router’s JSON. For summary: decision/denial/outcome counts, total spend, per-pool state with rationale, and the kill-test verdict lines (override rate vs 0.5, estimate bias vs the 10% SLO). For status: a one-line health summary. For outcome: confirmation with any metered_equivalent_burn_usd the router applied.

Troubleshooting

Symptom	Fix
“router unreachable”	Service down — the triage hook is falling back to static routing by design. Restart via /router-setup or the command in ~/.arthai/arth-router/router.log’s directory.
ARTH_ROUTER_URL unset	Run /router-setup (writes it to ~/.claude/settings.json); env loads in NEW sessions.
Everything routes to cheap models	Pool tight/exhausted or budget ≥ limit — check /router pools; that’s the policy working. Raise limits in ~/.arthai/arth-router/policy.yaml if wrong.
401/403 from the router	Auth is enabled on a shared instance — set ARTH_ROUTER_TOKEN or use an API key.

Related

• /router-setup — install and wire the router
• /routing — the static triage rubric (the fallback path)
• Arth Router repo: ArthTech-AI/arth-router (usage guide, scalability, enforcement docs)