- Let us find it - Call
/searchand we’ll find the most relevant information across all sources - Filter by source - Use
included_sourcesorexcluded_sourcesto target specific datasets
Why This Exists
Modern AI agents face a scaling problem: loading 50+ tool definitions into context consumes 10-20K tokens and degrades selection accuracy. Claude’s Tool Search solves this with deferred loading—tools are discovered at runtime, not loaded upfront. This API is built for that paradigm. Instead of hardcoding knowledge of available datasets, agents can:- Query
/datasources/categoriesto understand the landscape - Filter to relevant category
- Get full schemas only for datasources they need
- Use
example_queriesfor few-shot prompting
Quick Start
Filter by Category
| Category | Description | Example Sources |
|---|---|---|
research | Academic papers | arXiv, PubMed, bioRxiv |
healthcare | Medical data | Clinical trials, drug labels, WHO |
markets | Financial data | Stocks, crypto, forex, ETFs |
company | Corporate data | SEC filings, earnings, insider trades |
economic | Government stats | FRED, BLS, World Bank |
predictions | Prediction markets | Polymarket, Kalshi |
transportation | Transit data | UK Rail, ship tracking |
legal | Case law | UK legislation, court cases |
politics | Parliamentary data | UK Parliament |
patents | IP filings | Global patents |
List Categories
Get all categories with dataset counts:What’s in a Datasource
Each datasource includes everything an agent needs:Using with Search
Once you know which datasources you want, use them with the Search API:For AI Agent Developers
If you’re building agents that use Valyu as a tool:- Don’t hardcode datasources - Query this API to discover what’s available
- Use
example_queries- They’re optimized for few-shot prompting - Check
response_schema- Know exactly what fields to expect - Estimate costs with
pricing.cpm- Budget before making requests

