Skip to main content
Nimble code search helps a code search tool decide what to show a coding agent. You send a query and a list of items, where each item is a piece of a file or a folder. For each item, Nimble returns the probability that the agent needs it for the query. Send the request to POST /v1/systemone with one of the code search models. The request uses the System One format with noul questions, so clients that already send System One requests can use it.

Make a request

Question q0 is about item n0, question q1 is about item n1, and so on.

Read the answer

  • Keep the items whose noul is above 0.5. Nimble sets the scores so that this keeps about 95% of the items that an agent needs.
  • details.raw is the model’s own probability before that adjustment.
  • details.escalated says whether a larger model scored the item.
  • An item whose prompt is longer than 8,192 tokens is not scored. Its noul is 1.0, so you keep it, and overflow is true.
With the Python SDK, the extra fields are attributes of the response, e.g., response.details.

Models

The 27B model is running on weekdays from 07:30 to 19:00 Pacific time. At other times, it must start before it can answer. Until it is ready, a nimble-codegrep-max request gets 503 with a Retry-After header. So does a nimble-codegrep request with an item that the 4B model is unsure about. Starting takes a few minutes. You are not charged for a 503.

Limits

Use noul questions. Code search also accepts boolean questions, and it answers them the same way, with a noul answer. Send the state as an object with a query and items. Every item needs an id, a path and a kind. Question q<i> is about item n<i>, and a question ID with no matching item gets 422. Code search also accepts a string state and uses it whole for every question, but the models were not trained on that.