models get returns 404 for model IDs containing slashes

[majiayu000]

Problem

atlas models get MODEL_ID fails for real AtlasCloud model IDs that contain /, for example openai/gpt-5.1 and google/nano-banana-2/text-to-image.

The original source repo majiayu000/atlascloud-cli appears to be archived/read-only, so I am filing this against the active CLI distribution repo.

Reproduction

atlas version
atlas models get openai/gpt-5.1 --json
atlas models get google/nano-banana-2/text-to-image --json

Observed locally on 2026-05-14 with atlas-cli 0.1.0:

http_404: 404 page not found

atlas models list --json does return IDs such as openai/gpt-5.1, so IDs discovered by list/search cannot be passed back into models get.

Likely cause

The CLI source currently builds the schema request as:

path := "/v1/models/" + modelID

Most AtlasCloud model IDs are path-like (vendor/model, and sometimes vendor/family/task). A plain path segment route such as /v1/models/:model cannot capture the full ID after the first slash, so schema lookup returns 404.

Expected behavior

atlas models get <id from atlas models list> should work for all model IDs returned by list/search.

Possible fixes

• Prefer a query-based endpoint, for example GET /api/v1/models/schema?id=..., or a server route that supports the full escaped ID.
• At minimum, URL-escape the model ID in the CLI and verify the server preserves escaped slashes end-to-end.
• Add an integration/contract test using a slash-containing ID such as openai/gpt-5.1 or google/nano-banana-2/text-to-image.