101 — ModelScope Studios and skills catalogs: no observed-label listings
Reviewed September 5, 2026, 21:24 UTC. Extends100 beyond model/dataset listings.

Documented scope and execution
The official modelscope_hub OpenAPI source captured in100 defines public GET /openapi/v1/studios and /openapi/v1/skills, both require_token=False and both accepting search/page_number/page_size. The Studio method documents a running-only default for general searches; status=all is explicitly supported. This pass supplied status=all to include stopped applications within the catalog's supported search scope.
Source: https://github.com/modelscope/modelscope_hub/blob/main/src/modelscope_hub/_openapi.py

Eight successful read-only requests
For each catalog, queried xinzhai, xz_knowledge_p1 and xz_improvement_plan_p1, with page_number=1&page_size=5. Studio requests additionally used status=all.
https://modelscope.cn/openapi/v1/studios
https://modelscope.cn/openapi/v1/skills
All six label queries returned HTTP200 and success=true. Studio results reported total_count=0 and studios=[]. Skill results reported total=0 and skills=null. The different schemas were preserved, not silently interpreted as identical arrays.
Positive controls searched Qwen: Studios returned five actual listings with total_count1,053; skills returned five actual listings with total127. These totals are observed server counts, not inspected totals. Only catalog metadata was retrieved; no applications, skills, models or inference endpoints were started, invoked, installed or downloaded.

Schema caveat
The inspected SDK comment says Studio listings lack the success/data envelope, but the current responses have that envelope. The review follows the actual captured responses. Source documentation establishes intended route semantics; it does not override runtime evidence or prove exact index coverage.

Interpretation
No xinzhai/xz listing was found in the checked application and skill catalogs. This does not search all Studio source files, logs, historical/deleted applications or every skill's file contents. Source-file global search remains unverified. The zero result is therefore bounded, and no attribution follows.

Access and provenance
Both public catalog routes work from the existing server without new geographic infrastructure. 101-private preserves all eight responses and exact URLs, timestamps and SHA-256 hashes in openapi-metadata.json. The SDK source provenance remains100-private/source-hashes.json. All requests were public GETs with pacing. No authentication, original Ubuntu access, source execution, key search or decryption occurred. No new bot wave;173terminal reports unchanged, no live job remains.