Fi Money
Fi Money is a Bengaluru, India based money-management application and consumer fintech operated by Epifi Technologies, founded in 2019 by ex-Google Pay (Tez) executives Sujith Narayanan and Sumit Gwalani together with Neeraj Bhope and Prasanna Ranganathan. Fi is not a chartered bank; it delivers a millennial-focused mobile experience layered on top of partner RBI-licensed Federal Bank, providing zero-balance digital savings accounts, a Visa debit card, deposits, mutual funds, Indian and US stocks, EPF tracking, credit cards, personal loans, jump-style automated savings rules ("FIT Rules"), and an AI-powered money assistant. Fi has raised roughly US$169M across multiple rounds from investors including Sequoia Capital India (Peak XV), Ribbit Capital, Temasek, Alpha Wave, and B Capital, and serves Indian retail consumers via iOS and Android apps. There is no classic public REST developer API or partner banking-as-a-service surface; Fi's only developer-facing interface is the Fi MCP (Model Context Protocol) server — a JSON-RPC streaming endpoint at https://mcp.fi.money:8080/mcp/stream that lets users connect their own Fi account to LLM clients (Claude Desktop, Cursor, Windsurf, Gemini, ChatGPT) and call read-only tools such as fetch_net_worth, fetch_credit_report, fetch_epf_details, fetch_bank_transactions, fetch_mf_transactions, and fetch_stock_transactions to expose their net worth, holdings, EPF balance, credit report, and transactions to AI assistants. A hackathon-friendly mock server (epiFi/fi-mcp-dev, Go) and developer documentation (epiFi/mcp-docs) are published publicly on GitHub.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Fi Money the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Fi Money scores 16.0/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fi Money
Each block below is one kind of artifact we hold for Fi Money. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Fi Money — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fi-money · machine-readable index on apis.io