Redpine Connect
API referenceSearch

Assisted search (verified results only)

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.

POST
/api/v1/search/assisted

Authorization

BearerAuth
AuthorizationBearer <token>

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

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/api/v1/search/assisted" \  -H "Content-Type: application/json" \  -d '{    "query": "string"  }'
{  "billing": {    "chargedResults": 0,    "tokensCharged": 0  },  "clarification": {    "question": "string",    "reason": ""  },  "filterWarnings": null,  "iterationsRun": 0,  "journalMetricExpansions": null,  "latencyMs": 0,  "queryId": "string",  "queryUnderstanding": {    "aspects": [      "string"    ],    "entities": [      "string"    ],    "filters": {},    "intent": ""  },  "results": [    {      "collection": null,      "doiUrl": null,      "id": "string",      "metadata": null,      "relevance": {        "judgeScore": 0,        "matchedTerms": [          "string"        ],        "rationale": ""      },      "section": null,      "text": "string"    }  ],  "status": "results"}
Was this page helpful?