/modelscope/studios/search

POST /api/modelscope/studios/search

Price: 5 credits

Search ModelScope studios (Gradio/Streamlit apps)

How to use it

Search ModelScope studios (hosted Gradio/Streamlit demo apps) by keyword and creation type. Sort by trending, downloads, or likes. Returns studios with likes, visits, tags, SDK type, running status, app URL, and linked organization.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text search keyword (examples: "qwen")
• create_type array nullable — Filter by how the studio was created (interactive builder or programmatic upload) (one of: "interactive", "programmatic")
• sort string — Sort order (default: "trending"; one of: "trending", "downloads", "likes")
• count integer required — Max result count (min: 1)

Response

• @type string (default: "ModelScopeStudio")
• id string required
• url string required
• name string nullable
• owner string nullable
• chinese_name string nullable
• description string nullable
• like_count integer nullable
• download_count integer nullable
• predict_count integer nullable
• visit_count integer nullable
• unique_visitor_count integer nullable
• tags array (default: [])
• domain array (default: [])
• license string nullable
• studio_type string nullable
• status string nullable
• sdk_type string nullable
• sdk_version string nullable
• app_url string nullable
• is_published boolean (default: false)
• is_mcp_server boolean (default: false)
• is_login_required boolean (default: false)
• visibility integer nullable
• revision string nullable
• created_by string nullable
• created_at integer nullable
• updated_at integer nullable
• deployed_at integer nullable
• image string nullable
• cover string nullable
• related_paper_ids array (default: [])
• organization object nullable
  • @type string (default: "ModelScopeOrganization")
  • id integer nullable
  • name string nullable
  • full_name string nullable
  • image string nullable
  • github_url string nullable
  • created_at integer nullable
  • updated_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.