面向 AI 智慧代理的網頁搜尋 API
為 LLM 工具呼叫打造的即時網頁搜尋端點。可預測的 JSON 輸出、國家與日期篩選,並依呼叫計點 — 可接入 OpenAI 函式呼叫、Claude 工具使用或任何智慧代理框架。
API Integration Guide
Learn how to integrate this API into your applications with code examples and detailed documentation.
/api/search/webBase URL
https://www.apipick.comFull Endpoint
https://www.apipick.com/api/search/webqueryNatural-language search query
max_num_results1–5, default 5
relevance_threshold0.0–1.0 quality filter
country_codeISO country code (e.g. US, GB)
start_dateISO date YYYY-MM-DD
end_dateISO date YYYY-MM-DD
cURL Request
curl -X POST "https://www.apipick.com/api/search/web" \
-H "Content-Type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{
"query": "latest developments in quantum computing",
"max_num_results": 5,
"country_code": "US",
"start_date": "2026-01-01"
}'YOUR_API_KEY with your actual API keyJSON Response
{
"query": "latest developments in quantum computing",
"results": [
{
"title": "Example result",
"url": "https://example.com/article",
"snippet": "Short excerpt of the page content…",
"source_type": "web",
"published_at": "2026-04-15",
"score": 0.92
}
],
"result_count": 1,
"credits_used": 15,
"remaining_credits": 99
}✓Best Practices
- • Always include x-api-key header
- • Always handle errors gracefully
- • Validate input data before sending
- • Use HTTPS for secure communication
- • Cache responses when appropriate
ℹResponse Headers
- • Content-Type: application/json
- • x-api-key: Required for authentication
- • Status codes: 200 (success), 400 (error), 401 (unauthorized)
- • No rate limiting applied
Rate Limits
Request Rate
60req / min
Per API key, per endpoint. Sliding 60-second window.
Concurrency
3concurrent
Max simultaneous in-flight requests per API key.
Response Headers
429 Too Many Requests
HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 12
{
"error": "rate_limit_exceeded",
"message": "Rate limit exceeded: 60 requests/minute per API key. Retry after 12s.",
"retry_after": 12
}常見問題
與 Google 或 Bing 搜尋 API 有何不同?
回應已為 LLM 消費預先成型:短摘要(無樣板)、結構化 JSON、相關性分數。在送進模型前不必額外做抓取與清理步驟。
結果如何排序?
結果以語意嵌入排序,而非關鍵字比對,因此即使措辭不同,意義相近者也會靠近。也可傳入 relevance_threshold(0.0–1.0)來過濾低品質結果。
可以限制特定國家或日期範圍嗎?
可以。傳入 country_code(ISO 3166-1 alpha-2,如 US、JP)和/或 start_date / end_date,格式為 YYYY-MM-DD。
失敗的呼叫如何計費?
若搜尋失敗(5xx 或無效查詢),不扣除點數。僅對成功的 2xx 回應計費。
有給 OpenAI 函式呼叫的工具 schema 嗎?
有。GET /api/search/web/tool-schema 回傳可直接貼上的 OpenAI 函式與 Claude 工具使用定義。