Research: fastCRW /v1/search API contract #3
Notifications
Due Date
No due date set.
Blocks
#5 Grilling: config surface for endpoint and token
haylan/fastcrw-opencode-websearch
Reference: haylan/fastcrw-opencode-websearch#3
Reference in new issue
Block a user
Map: #1
Question
What is the fastCRW self-hosted
POST /v1/searchcontract? 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 officialcrw-mcpexposes that the REST API makes unnecessary.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.