APIs & MCP Servers from Tigzig

Serve structured datasets. Hit the query endpoints, or download the whole database in one file (CSV / TSV / Parquet / SQLite / DuckDB).

Send inputs (tickers, a portfolio) and get a computed report or dataset back. Each is open source and also runs as an MCP server over the same backend.

MCP tools and utility services over the same infrastructure.

• 2 Oct 2026 FY 2025-26 BRSR data is live for 663 of the 750 Nifty Total Market companies: workforce, pay and complaints VIGIL
• 1 Oct 2026 Jev Rank on the News section scores every headline from 0 to 100 against what you want to read, and sorts the page TREMOR
• 20 Sep 2026 Point an AI agent at the cricket database with one pasted line, and it works out the rest Cricket DB
• 20 Sep 2026 August 2026 portfolios live on Composition, taking it to 11 month-end snapshots across 24 equity funds MFPRO
• 20 Sep 2026 Quant and portfolio reports consolidated into one app, with three ways in, and the agent now looks up symbols live QDESK
• 19 Sep 2026 NCUA Q2 2026 credit union data is live: 88 quarters of balances, delinquency and charge-offs TREMOR

Everything that changed, newest first - filter it by app on the page.

The pages above are the reference - what each API is and how to call it. These are the long-form guides: worked examples, the mistakes real callers actually make, and what to do when something returns an error. Each is a plain page with a Markdown twin, so you can hand the URL straight to an agent.

Every API

• Demystifying the API errors - what each error actually means and what to do about it, instead of guessing from a status code. Covers every TigZig API, not just this one.
• Your agents and scripts have been talking to me - what real callers actually do, read out of the server logs: the common mistakes, what works, and the patterns worth copying.
• Is it you, or is it me? - the public status page for every TigZig API, so you can check whether a failure is at your end or ours before you start debugging.

India mutual fund NAV

• Free AMFI mutual fund NAV API for India - what the data is, how to pull one scheme, and how to take the whole dataset in a single call.
• Search filters across 12 fields on a scheme - the full walkthrough of the browse filters on this page: how they combine, what a wrong call looks like, and the limits worth knowing before you rely on a result.
• Three ways to pull NAVs in far fewer calls - batching, the bulk files and the Parquet route, with the trade-off on each so you can pick one to suit the size of your job.
• Pull NAVs straight into Excel - the spreadsheet route for 50, 100 or more schemes, with no code involved.

Database (SQL + MCP)

• A database server you can point an AI agent at - what this service is, with ball-by-ball cricket behind it: the REST API, the MCP server, and what an agent does with each.
• Run your own SQL on the cricket database - worked queries against T20 and ODI ball-by-ball data, free and with no key, plus what the row caps mean in practice.
• Taking the whole dataset as files - the download paths, how the file names are formed, and when a bulk pull is the better move over a query.

Yahoo Finance

• Pulling Yahoo Finance data into your own tools - the four routes in: Excel, Google Sheets, a web tool, or straight from an AI agent.
• An Excel tracker for hundreds of tickers - a full worked build with xlwings Lite, for when Excel WEBSERVICE keeps failing on volume.
• 25 tickers in one request - what changed on the backend: batching, answers in seconds, and a clear error when something is wrong.

TREMOR macro data

• A free API for 330+ macro and market indicators - what is in the dataset, how often it refreshes, and how to have an agent explore it without writing any code.

VIGIL India red flags

• Take the whole VIGIL database in one call - the bulk download covering every red-flag dataset here, and the single API call that pulls the lot.

Markdown to PDF

• Markdown to PDF over the API - the typesetting options, what each one does to the output, and a call you can paste. No signup and no key.
• The rebuilt converter - what changed in the rebuild, the web page for pasting text straight in, and the MCP route for an agent.

Technical analysis

• Technical analysis without visiting the site - how to ask an AI agent for a read on any ticker, and what comes back.

QRep / QuantStats

• Four routes into QuantStats - comparing securities on returns, risk and drawdowns, with the route to pick set by what your AI can already do.

Published limits are per IP, so a well-behaved client can plan around them. Cross one and you get HTTP 429 with Retry-After and a JSON body naming the limit hit and what to do instead (typically: batch, or use the bulk download rather than paginating). Honor the header for clean back-off. These figures are current at build time - the numbers that cannot go stale are the X-RateLimit-* headers on your own successful responses and each API's discovery endpoint, both linked from the per-API page.

Legacy: an earlier Tremor V1 surface is still served at /tremor/v1/* (REST) and /tremor/v1/mcp/http (MCP). It is frozen - response shape stable, data still refreshed daily - and stays mounted for existing integrations (limits 10-30 req/min per IP). New work should use the unified /v1/* surface above.

Sample 429 response

HTTP/1.1 429 Too Many Requests
Retry-After: 60

{
  "detail": "Rate limit exceeded",
  "limit": "60 per 1 minute",
  "retry_after_seconds": 60,
  "suggestion": "For multi-indicator or long-history pulls use the bulk download endpoints instead of paginating: GET /v1/download/all (sqlite | duckdb) for the full dataset, or /v1/download/{table}?format= for one table. One request vs many.",
  "limits_doc": "https://api.tigzig.com/v1/"
}

Per-call caps (unified /v1 series + indicators endpoints)

• Max 10 indicators per /v1/series call - pass more by chunking, or hit /v1/download/{table} for the whole table in one file
• Max 10,000 rows per response - reduce the date range, or use a bulk download for full history
• TSV output carries a # meta: count=N unknown=[...] empty=[...] comment line so the agent can detect typo'd ids in the body

Heavy pulls: use bulk downloads, not pagination

If you need many indicators or long history, do not paginate /v1/series - use bulk downloads instead. One bulk request avoids rate limits entirely and serves you a single file you can query locally.

• GET /v1/download/all?format=sqlite (or duckdb) - every public table in one file
• GET /v1/download/{table_name}?format=parquet - one table (macro_indicators, stock_prices, or indicator_config)
• GET /v1/downloads/manifest - file sizes + last-refresh timestamp

Programmatic consumers: the live numbers are also available at GET https://api.tigzig.com/v1/ under the limits block (per_ip_per_minute, per_ip_downloads_per_minute, max_ids_per_series_call, max_rows_per_response). Read it once at startup; do not hard-code.