Anonymous request (per-IP free quota)
- 1
- 2
- 3
- 4
- 5
- 6
curl -X POST https://api.anysearch.com/v1/search \
-H "Content-Type: application/json" \
-d '{
"query": "What is quantum computing?",
"max_results": 5
}'
Unified search infrastructure for AI
https://api.anysearch.comTwo steps to plug AI-grade search into your app: grab an API key from the dashboard (or skip it and try the free anonymous tier), then fire your first search request.
curl -X POST https://api.anysearch.com/v1/search \
-H "Content-Type: application/json" \
-d '{
"query": "What is quantum computing?",
"max_results": 5
}'
curl -X POST https://api.anysearch.com/v1/search \
-H "Authorization: Bearer ss_sk_your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"query": "What is quantum computing?",
"max_results": 5
}'
The AnySearch search API (/v1/*) supports flexible authentication. You can decide whether to send an API key based on where you are in your product lifecycle:
The unified search endpoint. The gateway routes the query to the best providers based on intent, then fuses and re-ranks the results.
API key optional (anonymous traffic is rate-limited per IP and consumes the daily free quota)
Request parameters
Request example
curl -X POST https://api.anysearch.com/v1/search \
-H "Authorization: Bearer ss_sk_test_key" \
-H "Content-Type: application/json" \
-d '{
"query": "Go 1.22 release notes",
"max_results": 5,
"domains": ["code", "tech"],
"content_types": ["web", "doc"]
}'
Response example
{
"results": [
{
"title": "Go 1.22 Release Notes",
"url": "https://go.dev/doc/go1.22",
"description": "Go 1.22 is a major release...",
"content": "Detailed content here...",
"source": "web",
"score": 0.87,
"quality_score": 0.95,
"published_at": "2024-02-06T00:00:00Z"
}
],
"metadata": {
"total_results": 1,
"search_time_ms": 342,
"routes_queried": 2,
"routes_succeeded": 2,
"request_id": "req_abc123"
}
}
A successful 200 response returns a JSON body with a results array and a metadata object.
Result fields
Metadata fields
Full response example
{
"results": [
{
"title": "Chernobyl disaster - Wikipedia",
"url": "https://en.wikipedia.org/wiki/Chernobyl_disaster",
"description": "The Chernobyl disaster began on 26 April 1986 ...",
"content": "On 26 April 1986, reactor No. 4 ...",
"raw_content": "...",
"source": "web",
"score": 0.87,
"quality_score": 0.78,
"signal_scores": {
"freshness": 12,
"authority": 31
},
"published_at": "1986-04-26T01:23:00Z"
}
],
"metadata": {
"total_results": 5,
"search_time_ms": 412,
"routes_queried": 2,
"routes_succeeded": 2,
"request_id": "req_01HXXXXXXX",
"cached": false,
"capability_errors": []
}
}
Every error response includes a request_id field. 429 responses also carry Retry-After and X-RateLimit-* headers.
Error response example
{
"code": "quota_exhausted",
"error": "quota exhausted",
"message": "You've hit your quota limit. Top up to keep using the API.",
"request_id": "req_xxx"
}
Allowed values for the enum fields most commonly used in API calls.