Search a single collection by name
Shorthand for POST /api/v1/search/query with the collection named in the path instead of the body. Same pipeline, same response shape, one collection per call — use /query's `collections` form to search several at once.
Authorization
BearerAuth API key authentication. Pass your key in the Authorization header as Bearer sk_live_.... An X-API-Key: sk_live_... header is also accepted as an alternative. Keys are created in the Redpine Connect dashboard under Settings > API Keys.
In: header
Path Parameters
Name of the collection to search.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Same knobs as SearchRequest minus collection/collections — the target collection is the path segment, so a collection key in the body is rejected.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/v1/search/string" \ -H "Content-Type: application/json" \ -d '{ "query": "string" }'{ "filterWarnings": null, "journalMetricExpansions": null, "latencyMs": 0, "queryId": "string", "results": [ { "collection": null, "id": "string", "metadata": null, "text": "string" } ]}Assisted search (verified results only) POST
Agentic search: the query is interpreted, one or more internal searches are planned and run, every candidate is verified as actually addressing the query, and only verified results are returned. **Billing differs from `/search/query`:** only delivered, verified results are charged. A clarification request or an honest no-results answer costs nothing. Internal search fan-out and LLM tokens are absorbed by Redpine. Accepts the same `filters` as `/search/query`, applied to every internal search.
Search documents POST
Search one or more collections using natural language or keyword queries. Results are ranked by relevance using hybrid retrieval (dense + sparse + reranking). Pass `collections` (up to 5) to search several collections in one call and receive a single merged, relevance-ranked list with per-result origin labels.