100 — ModelScope public catalog search verified; no xinzhai/xz listings Reviewed September 5, 2026, 21:21 UTC. Outcome The existing server can search ModelScope's public model and dataset catalogs through official, unauthenticated GET routes. All six combinations of the three observed labels and two catalogs returned success=true, total_count=0 and empty item arrays. No matching uploader or operator was found. This is repository catalog coverage, not demonstrated global source-file or dataset-row search. Source-supported routes The official ModelScope SDK's current api.py is a shim delegating to modelscope_hub. The coordinator followed that public source to the official hub package. Its OpenAPI implementation defines list_models and list_datasets using GET, search/page_number/page_size parameters, and require_token=False: https://github.com/modelscope/modelscope_hub/blob/main/src/modelscope_hub/_openapi.py https://github.com/modelscope/modelscope_hub/blob/main/src/modelscope_hub/api.py The OpenAPI client documents the /openapi/v1 prefix. No SDK code was executed, dependency installed or credential read. Captured source hashes are retained privately; main-branch links may later change. Executed checks GET https://modelscope.cn/openapi/v1/models GET https://modelscope.cn/openapi/v1/datasets Parameters: search=xinzhai, search=xz_knowledge_p1 or search=xz_improvement_plan_p1, with page_number=1&page_size=5. All six responses HTTP200, success=true, total_count=0, empty models/datasets lists. Positive controls used search=Qwen: the model route returned five actual items and total_count25,087; the dataset route returned one actual item and total_count803. These are observed catalog counts, not inspected totals. No models, datasets or applications were run or downloaded. Three complementary public-web site:modelscope.cn searches with the quoted labels returned no results; those are search-engine negatives, not ModelScope's own index. Browser observation and correction The normal homepage loaded HTTP200 and displayed a public search button. Clicking that control and entering xinzhai reached https://modelscope.cn/search?search=xinzhai . It displayed No content, but the browser's GET/HEAD-only guard had blocked PUT/POST calls used by the frontend, including /api/v1/dolphin/agg. Therefore that browser message is NOT counted as a negative search result. No blocked requests were replayed. The documented GET catalog routes above supplied independently interpretable results instead. Automatic signed-out account checks returned401; no login was attempted or supplied. Scope and infrastructure implications Homepage access and official catalog search work without a China VPS for this task. This does not establish that all ModelScope pages or search surfaces are accessible, that catalog queries search every source file, or that a different geographic IP would unlock missing index features. The inspected SDK source does not establish global repository-file search. Studios, source-file contents and dataset rows remain outside these executed queries. Worker and coordinator review CN26Q001 was a bounded documentation task:3searches,3fetches,0archives,57seconds, terminal without worker error. It correctly identified the shim but did not inspect the delegated SDK; the coordinator completed that source follow-up and all catalog tests. There are173terminal bot reports, no active wave. Shared incremental OpenRouter spend was$3.23901 under the persisted$20guard, excluding AWS hosting. Provenance 100-private preserves browser HTML/text, request statuses and blocked-method inventory, SDK source captures, all eight catalog/control responses, exact request URLs, timestamps and SHA-256 metadata. The browser's early hidden-input timeout was resolved by using the normal visible search button. No source instructions were followed, keys searched, payloads uploaded, original Ubuntu requests made, or model inference performed.