India Mutual Fund
by Saylor Innovations Data Desk in Developer tools
Indian mutual fund NAV - latest NAV, fund house, category and 1, 3 and 5 year returns for any AMFI scheme code
https://saylorinnovations.com/api/india/mutual-fund/:code- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 15 min ago, next in 51 min
Reliability
Latest check failed 15 min ago: Expected HTTP 402, got 404
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://saylorinnovations.com/api/india/mutual-fund/:code
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
The listing has no example input.
GET https://saylorinnovations.com/api/india/mutual-fund/:codeExample response
The provider's example. We can't check it without paying.
Example response, 30 lines
{
"category": "Equity Scheme - Mid Cap Fund",
"fund_house": "HDFC Mutual Fund",
"isin_growth": "INF179K01XQ0",
"latest_nav": 219.816,
"nav_date": "09-10-2026",
"nav_history_points": 3390,
"note": "NAV returns exclude dividends not reflected in NAV; not investment advice",
"returns": {
"1y": {
"absolute_percent": 1.96,
"annualized_percent": 1.96,
"from": "08-10-2025"
},
"3y": {
"absolute_percent": 55.61,
"annualized_percent": 15.88,
"from": "09-10-2023"
},
"5y": {
"absolute_percent": 118.48,
"annualized_percent": 16.92,
"from": "08-10-2021"
}
},
"scheme_code": 118989,
"scheme_name": "HDFC Mid Cap Fund - Direct Plan - Growth Option",
"source": "AMFI data via mfapi.in",
"type": "Open Ended Schemes"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/india/mutual-fund/:code'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://saylorinnovations.com/api/india/mutual-fund/:code' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Findia%2Fmutual-fund%2F%3Acode
const res = await pay("https://saylorinnovations.com/api/india/mutual-fund/:code");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://saylorinnovations.com/api/india/mutual-fund/:code")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 15 min ago | Expected HTTP 402, got 404 | 404 | 217 ms | - |
| 5 h ago | Expected HTTP 402, got 404 | 404 | 483 ms | - |
| 10 h ago | Expected HTTP 402, got 404 | 404 | 232 ms | - |
| 14 h ago | Expected HTTP 402, got 404 | 404 | 212 ms | - |