s46.apiv1

Teams & sessions

Resolve authorized models and gateway configuration; list team sessions.

Resolve team metadata

GET/v1/teams/{team}→ 200 / 503

Auth · bearer / cookie

Path-escape the canonical team ID: @s46/engineering becomes %40s46%2Fengineering. Use the returned endpoint, region, and authorized models rather than hard-coding them. defaultModel is a configured preference: check that it appears in models before selecting it.

curl 'https://api.s46.dev/v1/teams/%40s46%2Fengineering' \
  -H "Authorization: Bearer $S46_ACCESS_TOKEN"

Illustrative cloud response (limits come from the verified registry, not client constants):

{
  "name": "@s46/engineering",
  "organizationSlug": "s46",
  "slug": "engineering",
  "endpoint": "https://gateway.s46.dev",
  "region": "EU-OPO",
  "mode": "cloud",
  "workerHosts": [],
  "defaultModel": "s46/example-published-model",
  "models": ["s46/example-published-model"],
  "modelMetadata": {
    "s46/example-published-model": {
      "contextWindow": 32768,
      "maxTokens": 4096,
      "reasoning": false
    }
  }
}

The response above is fictional contract data, not a claim that any named model is live. On this public cloud resolution route, models contains only servable, team-allowed IDs; modelMetadata maps those same IDs to signed runtime metadata. Admin team settings are configured values, not this authorized discovery view. Runtime fields include engine/version, profile digest, context/output limits, reasoning capability, and memory hints; optional fields may be absent. This authenticates metadata, not loaded checkpoint bytes. Airplane teams use local settings and may return modelMetadata: null.

When independent verification is required but unavailable, cloud resolution returns 503 model_registry_unavailable. An empty authorized list is not permission to use an arbitrary model. Optional development overrides are endpoint, region, mode, and defaultModel.

List sessions

GET/v1/sessions?team={team}→ 200

Auth · bearer / cookie

curl 'https://api.s46.dev/v1/sessions?team=%40s46%2Fengineering' \
  -H "Authorization: Bearer $S46_ACCESS_TOKEN"

Returns { "sessions": [...] }. Each session contains id, state, harness, location, region, model, age, spent, and task. Use region, not lane. This route lists sessions; it does not expose remote session-control actions.

On this page