Financial context for agents - TickerDB

# TickerDB - Financial context for agents. > Pre-computed market data that improves agent reasoning, reduces token usage, and replaces custom data pipelines. For complete API documentation including all endpoints, parameters, response fields, and categorical bands, see: https://tickerdb.com/llms-full.txt TickerDB provides pre-computed market data that improves agent reasoning, reduces token usage, and replaces custom data pipelines. ## Base URL https://api.tickerdb.com/v1 ## Coverage - Asset Classes: US Stocks, Crypto, ETFs - Tickers: 12,000+ - History: 5 years - Timeframes: Daily, Weekly - Update Frequency: End-of-day (EOD) - Response Format: JSON - Authentication: Bearer token ## Core Endpoints (The Four Doors) - GET /v1/summary/{ticker} — Full categorical snapshot for a single asset. Supports 4 modes: latest (no params), historical snapshot (date param), date range (start/end params), and event lookups (field/band params with optional cross-asset correlation). - GET /v1/search — Query the database with arbitrary multi-field filters. Accepts a JSON array of {field, op, value} filter objects. Supports eq, neq, in, gt, gte, lt, lte operators. Supports a `fields` param to select which columns to return (JSON array or comma-separated), dramatically reducing token usage. Call /v1/schema/fields first to discover available fields. - GET /v1/schema/fields — Returns all queryable fields with their types, valid values, and descriptions. Always free (0 credits). Call this before using search to discover what you can filter on. - GET /v1/watchlist — Summaries for saved tickers with field-level change detection. Also: POST (add tickers), DELETE (remove tickers), GET /v1/watchlist/changes (state diffs). ## Supporting Endpoints - GET/POST/PUT/DELETE /v1/webhooks — Push notifications for watchlist changes - GET /v1/account — Plan tier, limits, and current usage - GET/POST /v1/team — Team management for commercial plan