Search for market data API endpoints and built-in finance functions by natural language query. Use this FIRST to find the right endpoint before calling call_api. Covers stocks, options, forex, crypto, futures, indices, ETFs, and economic data. Pass market to pin results to a specific asset class when you already know it; omit it and the server will infer from the query. Use detail="more" to see query parameter docs needed for building call_api requests.

Fetch data from a Massive.com REST API endpoint. Use a path from search_endpoints results. Set store_as to save results as an in-memory table for SQL querying with query_data. Paginated responses include a next-page hint with the exact path and params for the follow-up request. The apply parameter runs built-in functions on results — string input values refer to table columns, numeric values are literals. Use search_endpoints with scope="functions" to discover available functions.

Run SQL queries on tables stored via call_api's store_as parameter. Special commands: SHOW TABLES, DESCRIBE , DROP TABLE . Tables auto-expire after 1 hour. Supports CTEs, window functions, JOINs, and ILIKE.

Full-text search: any stored table with TEXT columns is searchable directly via FTS5. Use WHERE {table} MATCH 'query' and ORDER BY rank (lower = better). Numeric columns preserve their types. For long TEXT fields (news body, 10-K risk factors, filings) prefer snippet()/highlight() in SELECT instead of the raw column — full paragraphs can be thousands of tokens each.

Recommended FTS pattern:

1. Find matches compactly: SELECT rowid, category, bm25({t}) AS score, snippet({t}, 4, '[', ']', '...', 15) AS snip FROM {t} WHERE {t} MATCH 'supply chain OR supplier' ORDER BY rank

2. Fetch the full body only for rows you need: call query_data again with SELECT supporting_text FROM {t} WHERE rowid IN (2, 7) and max_cell_chars=0.

Output cells over max_cell_chars (default 2000) are truncated with a visible marker; raise or set to 0 to disable.