Why Use the DeepSearch API
The DeepSearch API provides AI ready search results that enable:- Comprehensive Coverage - Search web, research journals, books, and live financial data
- Real-Time Results - Access up-to-the-minute information from sources
- Precise Filtering - Control sources, dates, relevance scores, and result count
- RAG-Ready - Perfect for Retrieval-Augmented Generation and AI agent workflows
Key DeepSearch Features
Multi-Source Search
Search web content alongside research papers, books,
and financial market data in one API call.
AI Ready
Get AI ready search results that can you pass directly to your AI’s context
window.
Source Control
Include or exclude specific domains, URLs, and datasets to focus on
authoritative sources.
Date Filtering
Filter results by publication date to get recent
or historical content.
Getting Started
Basic Search Query
Search across all available sources with a simple query:Fast Mode for Reduced Latency
Enable fast mode for quicker search speed but shorter results. Best for general purpose queries:Search Type Options
Control which data sources to search:Type | Description | Best For |
---|---|---|
all | Search web and proprietary sources (default) | Comprehensive coverage |
web | Web search only | Current events, general topics |
proprietary | Research, financial, and premium sources only | Research, technical analysis |
Advanced Features
AI Agent vs User Queries
Optimize retrieval based on the caller type:Response Length Control
Control how much content is returned per result:"short"
: ~25,000 characters per result"medium"
: ~50,000 characters per result"large"
: ~100,000 characters per result"max"
: Full content available- Custom integer: Exact character count
Advanced Feature Guides
Check out our guides for other advanced features:Source Filtering
Include or exclude specific domains and datasets - Control exactly which sources to search for more targeted results
Date Filtering
Filter by time periods - Focus on recent content or historical data with
flexible date range controls
Prompting Guide
Craft effective search queries - Learn how to write queries that get the
most relevant results
Tips & Tricks
Optimize your searches - Advanced techniques for better performance and cost control
Response Format
Standard Search Response
Top-level fields
Field | Description |
---|---|
success | Indicates whether the search completed successfully |
error | Empty string on success; populated when warnings or errors occur |
tx_id | Unique transaction identifier for tracing and support |
query | The processed search query |
results | Ranked array of result objects |
results_by_source | Count of results returned per source type |
total_results | Total number of matches available for the query |
total_cost_dollars | Total cost of the request in USD |
total_characters | Combined character count across all returned results |
fast_mode | Present when the query ran in fast mode (omitted otherwise) |
Result fields
Field | Description |
---|---|
title | Title of the document or article |
url | Canonical URL for the result (tracking parameters may be appended) |
content | Extracted text content, trimmed according to the response_length |
description | High-level summary of the result |
source | High-level source category such as web or academic |
price | Cost in USD attributed to this individual result |
length | Character count returned for this result |
data_type | Data modality for the result (for example unstructured ) |
source_type | Specific source classification (see Source types) |
publication_date | ISO 8601 publication date when available |
id | Stable identifier or canonical reference for the result |
image_url | Images extracted from the page |
relevance_score | Ranking score between 0 and 1 indicating result relevance |
Source types
Type | Datasets | Description |
---|---|---|
general | valyu-wikipedia and similar general-reference corpora | General knowledge indexes (e.g., Wikipedia) served from LanceDB |
website | Brave web search pipeline (fast + full), Spider scraper fallback, LinkedIn processor | General web articles extracted or scraped by the web processing stack |
forum | Brave QA hits handled by the web processor | Community Q&A snippets surfaced when Brave supplies QA payloads |
paper | valyu/valyu-arxiv and other academic research indexes | Academic paper corpora (ArXiv, etc.) routed through the academic server |
data | Finance server market data integrations (quotes, FX, fundamentals, etc.) | Structured market metrics and analytics returned by the finance search pipeline |
report | valyu/valyu-sec-filings (SEC filings service) | Regulatory filing documents returned from the SEC microservice |
health_data | WHO Global Health Observatory ingestion | Global health indicator records delivered by the WHO handler |
clinical_trial | valyu/valyu-clinical-trials (ClinicalTrials.gov) | Structured clinical-study summaries produced by the clinical trials handler |
drug_label | valyu/valyu-drug-labels (FDA DailyMed) | Drug labeling content (warnings, dosing, contraindications) processed by the DailyMed handler |
grants | NIH RePORTER grants ingestion | NIH funding project data generated by the NIH handler |
Best Practices
- Be Specific: Use detailed queries for better search results
- Set Appropriate Price Limits: Balance cost with data quality needs
- Filter Results: Use parameters to get only the most relevant content
- Choose the Right Search Type: Match
search_type
to your use case - Monitor Costs: Track
price_per_result
andtotal_cost_dollars
in responses - Optimize for Tool Calls: Set
is_tool_call=true
for AI agent usage
Error Handling
Try the DeepSearch API
Explore the complete API reference with interactive examples and detailed
parameter documentation.