Building with the API? Open the developer docs
Finmagine API & MCP — free tier to test • Pro/Max for full access • REST + MCP
Master the API Explorer through a complete learning overview and interactive flashcards
The three Wave 1 guides covered discovery, pricing, and the contract. This guide covers the fastest way to actually try any of it — the Interactive API Explorer, a page that lets you fire a real request against any of Finmagine's 86 operations directly from your browser, with no code, no Postman collection to import, and no local setup.
Click any card to reveal the answer. Use the search box to find a specific topic.
Open developer/api-explorer.php, sign in if you haven't already, paste an API key into the key bar at the top, and you're ready — there's no SDK to install, no Postman collection to import, no local server to run.
| Traditional path | API Explorer path |
|---|---|
| Read the docs, write request code, run it locally, debug | Click an endpoint, click Run, read the response |
| Install an HTTP client (curl, Postman, Insomnia) | Nothing to install — it's a page in your browser |
| Manually construct query strings and headers | Parameters are form fields; the request URL builds itself as you type |
| Guess at what a response looks like from prose docs | See the actual, live JSON response for that exact call |
A tab bar at the top switches the entire page between two views:
The India tab lists every Indian-market REST operation, grouped by category (Core, Company Intel, Market Intel, AI Content, Feeds), each with a colour-coded HTTP method badge and a tier badge (Free / Pro / Max) so you can see at a glance what a given key can call.
The US tab is deliberately different: it lists REST operations and the equivalent MCP tools as separate, individually selectable entries — grouped "— REST" and "— MCP" — so you can compare the two calling conventions for the same underlying data directly. Selecting an MCP tool shows a JSON-RPC 2.0 payload preview instead of a URL, and the Run button POSTs it live to /api/mcp.php exactly the way Claude or any other MCP client would.
Clicking any endpoint in the sidebar opens a request panel with:
Clicking Run fires a real HTTP request — not a simulated or cached example response. Whatever the live API returns right now for that exact call is what you'll see.
Every response panel shows three things above the body:
| Element | What it tells you |
|---|---|
| Status badge | Colour-coded — green for 2xx (success), orange for 4xx (client error, e.g. bad tier or missing param), red for 5xx (server error) |
| Response time | Milliseconds elapsed for that specific call, measured client-side |
| Request URL / tool name | The exact URL called (REST) or MCP tool name invoked, for copy-paste reference |
Below that, the full JSON response is syntax-highlighted — keys in blue, strings in green, numbers in red, booleans in magenta, null in grey — the same visual convention most API tools use, making it easy to scan a large payload for the field you actually care about.
The key bar includes a ⚡ Run All button (and a matching ⚡ Run All US on the US tab) that fires every REST endpoint in that market sequentially using their demo defaults, then shows a pass/fail summary row for each one — path, status, and a green or red indicator.
Five operations don't appear in the main endpoint list by default — they're gated behind a "Show LLM-powered endpoints" checkbox in the key bar, off by default. These are the operations that trigger an actual LLM call when you run them, rather than a straightforward database read:
| Operation | What running it does |
|---|---|
start_committee | Kicks off a real Investment Committee run — 5 requests per 24 hours per account, shared with the web UI |
start_preset | Kicks off a real Strategy Lab Research Preset — 10 requests per 24 hours per account, shared with the web UI |
test_byo_key | Makes a real ~15-second call to your own configured LLM provider to verify a BYO key works — rate-limited to 10 tests/hour, independent of your normal API limits |
screen_natural_language / us_screen_natural_language | Parses a plain-English screen query using Finmagine's own free-tier LLM key (Groq/Gemini) — no cost or provider quota to you; Free-tier accounts get 20 calls/day |
test_byo_key, making a live call to a third-party provider using your own credentials. Keeping them behind an explicit toggle means you never trigger one by accident while casually browsing the endpoint list.
For the operations that spend a real provider's tokens or a shared quota, the Run button doesn't fire on the first click — it arms on the first click and shows what it's about to do (which provider, and for a preset run, the actual preset and goal that will be sent), then fires only on the second click. This two-step pattern exists specifically so a stray click never triggers real spend.
It's worth being precise about this, since pasting a secret key into a web page is exactly the kind of thing to be cautious about: the Explorer page runs entirely in your own browser and calls fetch() directly against https://finmagine.com/api/... — the same live endpoint your own code would call. There is no intermediate proxy server that sees your key; the request goes straight from your browser to the real API, precisely once, per call you make.
localStorage if you explicitly want it remembered across visits — never sent to any Finmagine server except as the X-Api-Key header on the actual API call you triggeredThe Explorer is great for trying one operation in isolation. The next guide covers its counterpart for multi-step workflows:
See the API & Agent Integration hub for the full 12-guide roadmap.
Finmagine gives you 30+ computed financial ratios, sector benchmarks, FII/DII flows, the Finmagine Score, and AI-powered analysis — all in one place.