Pi

Pi reads providers from ~/.pi/agent/models.json. The sference launcher writes a sference provider block there and starts Pi with it selected.

Launch

curl -fsSL https://raw.githubusercontent.com/s-ference/sference/main/install.sh | sh
sference auth login --api-key 'sk_...'
sference launch pi

Pi starts with sference as the active provider and the full catalog in the model picker.

What the launcher writes

A sference provider in ~/.pi/agent/models.json, using Pi's openai-responses API against sference's /v1/responses:

{
  "providers": {
    "sference": {
      "api": "openai-responses",
      "baseUrl": "https://api.sference.com/v1",
      "apiKey": "sk_...",
      "models": [
        { "id": "zai-org/GLM-5.3", "name": "GLM 5.3", "reasoning": true, "input": ["text"] },
        { "id": "moonshotai/Kimi-K3", "name": "Kimi K3", "reasoning": true, "input": ["text", "image"] }
      ]
    }
  }
}

The model list is fetched live from GET /v1/models, so the picker mirrors your catalog exactly — including vision capability and context window per model.

Options

The launcher scopes Pi's picker to sference models by default (--models sference/**), so other providers you have configured stay hidden until you widen it. ** is required because sference model ids contain a slash.

Choosing a model

Cost control

• Prefix caching. Pi resends the system prompt and tool definitions every turn. Keep them stable and first so they bill at the cached rate — see Prompt caching.
• Cheap default, strong escalation. Set GLM-5.3-Flash as the active model and switch to Kimi-K3 for planning turns.
• Per-engineer attribution. Each engineer's key shows up separately in GET /control/v1/usage/by-key. See Usage & analytics.