Skip to main content
Fast search is the default mode. It returns results in approximately 1 second, making it suitable for real-time applications and high-volume workloads. 
curl "https://search-api.andisearch.com/api/v1/search?q=latest+AI+news" \
  -H "x-api-key: YOUR_API_KEY"
Fast search is the default — no depth parameter is needed. Setting depth=fast explicitly has the same effect.
  • Real-time search in user-facing applications
  • High-volume automated queries
  • AI agents that need quick answers
  • Applications where latency matters more than exhaustive coverage

​
Example response

{
  "results_type": "news",
  "answer": "",
  "type": "news",
  "title": "latest AI news",
  "results": [
    {
      "title": "Latest AI News and Developments",
      "link": "https://example.com/ai-news",
      "desc": "A roundup of the latest developments in artificial intelligence...",
      "source": "example.com",
      "type": "news"
    }
  ],
  "metrics": {
    "query": "latest AI news",
    "intent": "LatestNewsIntent",
    "duration": 890,
    "results_returned": 10,
    "total_results_found": 50
  }
}

​
Parsing the response

data = response.json()

# Check what type of results came back
print(data["results_type"])  # e.g., "news", "search", "images"

# Access results
for result in data["results"]:
    print(result["title"], result["link"])

# Check performance
print(f"Returned {data['metrics']['results_returned']} results in {data['metrics']['duration']}ms")
Get richer data from each result:
# Text extracts from result pages
curl "https://search-api.andisearch.com/api/v1/search?q=latest+AI+news&extracts=true" \
  -H "x-api-key: YOUR_API_KEY"

# Full metadata including content type and reader data
curl "https://search-api.andisearch.com/api/v1/search?q=latest+AI+news&metadata=full" \
  -H "x-api-key: YOUR_API_KEY"

# Markdown format for passing to LLMs
curl "https://search-api.andisearch.com/api/v1/search?q=latest+AI+news&format=context" \
  -H "x-api-key: YOUR_API_KEY"
metadata=full adds latency because it fetches additional data from each result page. Use metadata=basic (the default) unless you need contentType or reader data.
Fast searchDeep search
Response time~1 second~2–3 seconds
Spell correctionNoYes
Topic coverageSingle angleMultiple angles
Result qualityGoodThorough
Start with fast search. Switch to deep search when you need results a quick search might miss, or when thoroughness matters more than speed.

​
Next steps

Deep search

Enhanced search with spell correction and more sources.

Query parameters

Full parameter reference.

Basic search example

Complete integration with error handling.

Response format

Understand the response structure.