VIGIL API - Corporate Signals
Corporate events and red-flag signals for Indian listed companies, sourced directly from NSE public disclosures. Seven structured tables covering ratings, insider activity, pledges, takeovers, surveillance, and related-party transactions.
What you can do with it
- Pull all signals for a single company (one symbol, all tables)
- Track rating downgrades, pledge escalations, surveillance moves
- Build watchlists from RPT-heavy or pledge-heavy filings
- Cross-reference insider activity around price moves
- Generate red-flag alerts from daily refreshes
Refresh cadence
- Daily: credit ratings, insider trading, SAST, encumbrance events
- Quarterly: pledge data snapshot
- Snapshot: surveillance flags (latest stage)
- Half-yearly: RPT transactions (XBRL filing cycle)
The seven tables
Endpoints
Detailed Documentation
Per-table column reference, full data dictionary, upstream NSE source map, and downloadable snapshots. Lives inside the VIGIL Corporate Signals app.
vigil.tigzig.com/data-api
TREMOR API - Global Macro Indicators
~300 curated macro and credit-stress indicators from primary sources (FRED, OECD, RBI, MoSPI, ECB, NY Fed, NCUA, FDIC, Shiller, NSE). The data layer behind the TREMOR app, exposed as a public HTTP API and an MCP server.
What you get
- ~300 indicators across US, India, EU, global
- Full data dictionary - source, source series ID, unit, frequency, SA flag, first/last date, record count
- Time series in wide format (one row per date, one column per indicator)
- Filter dictionary by
category,country,source,frequency - JSON or TSV output on the series endpoint
Use cases
- Pull credit-stress signals (delinquencies, charge-offs, NDFI) without scraping primary sources
- Build your own macro early-warning dashboard
- Cross-source comparisons (e.g. NY Fed CCP + FDIC SDI + NCUA FPR on one chart)
- Wire indicators into a notebook or report-generator pipeline
- Let an AI agent (Claude, Cursor) pull data on its own via the MCP endpoint
Also available via MCP (for AI agents)
/tremor/v1/mcp/http
Streamable HTTP transport (recommended, MCP spec 2025-03-26)
/tremor/v1/mcp/sse
SSE transport (legacy fallback)
Two MCP tools: list_indicators (data dictionary), get_series (time series).
Full details on the dedicated MCP page: MCP Server: TREMOR.
Endpoints
Detailed Documentation
Full data dictionary with all indicators, interactive Swagger UI, every endpoint live-testable in the browser. Lives inside the TREMOR macro signals app.
tremor.tigzig.com/api
For AI Agents and Automated Discovery
All three APIs are listed in the site's standards-compliant catalog and are markdown-negotiable from any tigzig.com URL. An agent doesn't need to scrape HTML to learn the API surface - it can fetch one well-known JSON file.
Discovery endpoints
- RFC 9727 API Catalog: tigzig.com/.well-known/api-catalog (mirrored at api.tigzig.com) - linkset listing both APIs with their OpenAPI specs and Swagger docs.
- Robots / agent guidance: tigzig.com/robots.txt - directs agents to llms.txt, the API catalog, and the MCP servers directory.
- Site map for agents: tigzig.com/llms.txt - full site overview including these APIs, rate limits, and cross-links.
Markdown content negotiation
Send Accept: text/markdown on any tigzig.com page and the response is the structured markdown for that page, not the empty React SPA shell. Useful for agents that follow links from other pages without first knowing the llms.txt URL.
curl -H "Accept: text/markdown" https://tigzig.com/
Per-API discovery (well-known)
- api.tigzig.com/vigil/v1/openapi.json - Vigil API OpenAPI 3.1 spec
- api.tigzig.com/mf/v1/openapi.json - MF NAV API OpenAPI 3.1 spec
- api.tigzig.com/tremor/v1/docs - TREMOR API Swagger UI (interactive)
MCP endpoints (for AI agent integration)
api.tigzig.com/tremor/v1/mcp/http- TREMOR macro indicators via Streamable HTTPapi.tigzig.com/tremor/v1/mcp/sse- TREMOR macro indicators via SSE (legacy)- Full MCP server directory: tigzig.com/.well-known/mcp/servers.json