/groq/models/search

POST /api/groq/models/search

Price: 10 credits

Search the GroqCloud catalogue of production and preview models and Compound systems: price, developer-plan rate limits, token speed, context window and completion limits.

How to use it

Use it to compare what GroqCloud serves and at what price and rate limit. Enterprise rows read Contact Sales and carry no token price; audio models carry `price` with `price_unit` such as per hour or per 1M characters instead of input and output prices. Feed `id` into groq/models for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Keep only entries whose name, id or provider contains this text (examples: "gpt-oss")
• statuses array nullable — Keep only entries with any of these release statuses (one of: "production", "preview"; examples: ["production"])
• types array nullable — Keep only models or only Compound systems (one of: "model", "system"; examples: ["model"])
• count integer required — Max number of entries to return (min: 1)

Response

• @type string (default: "GroqModelRow")
• id string required
• url string required
• name string required
• tier string nullable
• model_type string required
• status string required
• provider_name string nullable
• provider_image string nullable
• tokens_per_second integer nullable
• input_price number nullable
• output_price number nullable
• price number nullable
• price_unit string nullable
• price_text string nullable
• rate_limits array (default: [])
• context_window integer nullable
• max_completion_tokens integer nullable
• max_file_size 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.