Research: fastCRW /v1/search API contract #3

Closed
opened 2026-10-03 13:44:10 +00:00 by haylan · 1 comment
Owner

Map: #1

Question

What is the fastCRW self-hosted POST /v1/search contract? Auth scheme and header, request fields and limits (query, limit, others), response shape (success, data[], error, snippet vs description), error codes, and rate/size limits. Also note anything the official crw-mcp exposes that the REST API makes unnecessary.

Map: #1 ## Question What is the fastCRW self-hosted `POST /v1/search` contract? Auth scheme and header, request fields and limits (`query`, `limit`, others), response shape (`success`, `data[]`, `error`, snippet vs description), error codes, and rate/size limits. Also note anything the official `crw-mcp` exposes that the REST API makes unnecessary.
haylan added the wayfinder:research label 2026-10-03 13:44:10 +00:00
haylan added a new dependency 2026-10-03 13:44:42 +00:00
Author
Owner

Research resolved: findings in docs/research/fastcrw-search-api.md (uncommitted). Key points: POST /v1/search with {query, limit<=20, lang, tbs}; Bearer CRW_API_KEY (none needed self-hosted unless CRW_AUTH__API_KEYS set); base URL CRW_API_URL; response data is flat array on hosted but data.results on self-hosted, so parse both; results carry both description and snippet; errors are {success:false,error,error_code}. Left open for review.

Research resolved: findings in docs/research/fastcrw-search-api.md (uncommitted). Key points: POST /v1/search with {query, limit<=20, lang, tbs}; Bearer CRW_API_KEY (none needed self-hosted unless CRW_AUTH__API_KEYS set); base URL CRW_API_URL; response data is flat array on hosted but data.results on self-hosted, so parse both; results carry both description and snippet; errors are {success:false,error,error_code}. Left open for review.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Blocks
Reference: haylan/fastcrw-opencode-websearch#3