Fix search endpoint documentation and navigation

api-reference/introduction.mdx

@@ -32,7 +32,7 @@ We offer a growing list of [first-party integrations](https://app.greptile.com/l
     </Step>
 
     <Step title="Search repos">
-        Optionally, use [`POST /search`](/api-reference/query) to search the repo or repos in natural language and get back just the list of relevant files, functions, classes etc., not the answer. 
+        Optionally, use [`POST /search`](/api-reference/search) to search the repo or repos in natural language and get back just the list of relevant files, functions, classes etc., not the answer. 
     </Step>
 </Steps>
 

api-reference/search.mdx

@@ -0,0 +1,12 @@
+---
+title: 'Search Repo(s)'
+openapi: 'POST /search'
+---
+
+Submit a natural language search query to find relevant code references without generating an AI response.
+
+Returns a list of relevant code files, functions, and snippets based on your search query, similar to the query endpoint but **without the AI-generated answer**.
+
+Use this endpoint when you only need the source references and don't need an AI explanation.
+
+Note: Before Greptile can search a repo, it must be indexed. See [Index Repository](/api-reference/index) for more information.

docs.json

@@ -55,6 +55,7 @@
               "api-reference/index",
               "api-reference/get-repository",
               "api-reference/query",
+              "api-reference/search",
               "api-reference/zapier"
             ]
           }