IVolatility

Search Endpoints

Search iVolatility API endpoints (and built-in finance functions) by natural language. USE THIS FIRST to find the right endpoint before calling call_api. Covers equity & futures options, implied volatility (IVX/IVS/skew), greeks, historical volatility, NBBO, EOD/intraday prices, earnings, account/access, and WebSocket discovery. For INSTRUMENT discovery — which tickers/roots/indices exist, index constituents (SP500/NASDAQ-100/DAX…), contract multipliers, "which stocks have listed options" — sear

Call Api

Fetch data from an iVolatility REST API endpoint (path from search_endpoints). Auth is automatic (apiKey). Large chains return a download link — fetched+unzipped transparently. store_as saves an in-memory table for query_data SQL. apply runs built-in functions (search_endpoints scope="functions"). PARAM CONVENTIONS — get these right or the API returns HTTP 400: - Dates are 'YYYY-MM-DD' literals. Range endpoints take from/to; single-date chains take date. - Option side: cp='C'/'P' (single char)

Query Data

Run SQL queries on tables stored via call_api's store_as parameter. Special commands: SHOW TABLES, DESCRIBE <table>, DROP TABLE <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()/hi

Export Data

Write one or more stored tables (from call_api store_as) to a single CSV file on disk under ~/ivolatility/MY_SAVED_DATA/. Pass several comma-separated tables to MERGE them into one file — e.g. export_data('calls,puts') writes the whole option chain in one file. Use this for full dumps / "save to file"; it writes ALL rows with no truncation, instead of streaming rows through the chat. Returns the file path. On the remote (URL) connector file export is disabled — deliver data v

Account Access

Show the user's OWN iVolatility entitlements: tariff/plan, which API methods they can call, quota/limits, and the reason for any 403. USE THIS whenever the user asks about their own account — "what is my tariff/plan", "what can I access", "which methods/endpoints are available to me", "requests left", "why do I get 403", "do I have access to X", or "where is my key". This is authoritative — do NOT answer such questions from guesses or by probing other endpoints, and do NOT sa