10router-add-providerlisted

# 10Router — Add a Custom Provider (Self-Serve) Lets an AI agent (or user) call the internal management API of a **running** 10Router to register a custom OpenAI/Anthropic-compatible upstream (baseUrl + its own key + models) as a routable node. **No source change / no repackage, no restart needed — live for subsequent `/v1/*` requests immediately.** Requires `TENROUTER_URL` (and an admin-capable auth key). Entry skill: https://raw.githubusercontent.com/techysy/10router/main/skills/10router/SKILL.md --- ## Confirm three things first | Item | Notes | |------|-------| | **Target URL** | `$TENROUTER_URL` (management API port follows your deployment; NAS/fnOS often `:20127`, adjust per instance) | | **Auth** | dashboard LLM key (below) or the deployer's own CLI token | | **Model routing** | custom-node models MUST be `{prefix}/{model}` — never a bare model name | ## Auth: dashboard LLM key (the self-serve exemption) Only **`POST /api/provider-nodes` and `POST /api/providers` at the root path** are open to a dashboard LLM API key (a key from Dashboard → Keys). GET/PUT/DELETE and `[id]` sub-routes still need the deployer's CLI token / login JWT. ```bash AUTH="Authorization: Bearer ${TENROUTER_KEY}" # TENROUTER_KEY = dashboard LLM key ``` > Deployers can also derive a CLI token on the host from `machine-id` + `cli-secret`: > `sha256(machine-id + "9r-cli-auth" + cli-secret).slice(0,16)`, fixed salt `9r-cli-auth`. > Custom data paths live under your DATA_DIR (`~/.10router/`