/ollama/models/search

POST /api/ollama/models/search

Price: 5 credits

Search Ollama library models by keyword and capability

How to use it

Search the Ollama model library by keyword, filtered by capabilities (cloud, embedding, vision, tools, thinking) and ordered by popularity or recency. Returns official and user models with description, pull count, tag count, capabilities, and parameter sizes.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Search keyword (default: "")
• capability array — Filter by model capabilities (default: []; one of: "cloud", "embedding", "vision", "tools", "thinking")
• sort string — Result ordering (default: "popular"; one of: "popular", "newest")
• count integer required — Number of results to return (min: 1)

Response

• @type string (default: "OllamaModel")
• name string required
• alias string required
• url string required
• description string nullable
• pull_count integer nullable
• tag_count integer nullable
• updated_at string nullable
• capabilities array (default: [])
• parameter_sizes array (default: [])
• is_official boolean (default: false)
• variants array (default: [])
  • @type string (default: "OllamaModelTag")
  • tag string required
  • digest string nullable
  • size string nullable
  • size_bytes integer nullable
  • context string nullable
  • input string nullable
  • quantization string nullable
  • parameter_size string nullable
  • updated_at string nullable
  • is_default boolean (default: false)
• readme string 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.