Skip to content
Clairos Learn

Inference requests and APIs · Lesson 2 of 16 · 9 min

List served models

A served-model list describes identifiers the gateway accepts. Use the exact served identifier rather than a local filename or an unrelated registry name.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

A served-model list describes identifiers the gateway accepts. Use the exact served identifier rather than a local filename or an unrelated registry name.

Interpret the evidence

Use assistant-stable or deliberately deploy the candidate before requesting it.

A tempting mistake

Assume every artifact in storage is a served model identifier.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-inference-apis-002.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "served_models": [
    "assistant-stable"
  ],
  "requested_model": "assistant-candidate"
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .served_models /opt/ai-lab/cases/aiops-inference-apis-002.json
[
  "assistant-stable"
]

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'use-served-id' > /home/learner/lab/aiops-inference-apis-002-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “use-served-id” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “List served models” justify?

Apply it elsewhere

A colleague concludes: “Assume every artifact in storage is a served model identifier.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Read a request envelopeTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Check gateway healthA health endpoint can describe process liveness without proving model readiness. Read the scope of the endpoint before using its status to approve traffic.Practice
  2. 02Read a request envelopeA request envelope combines model selection, messages and generation constraints. Invalid field types should be corrected at the contract boundary before retrying.Practice
  3. 03Read a response envelopeA response envelope contains output plus metadata such as completion status and usage. Inspect the finish reason before treating partial output as a complete answer.Practice