Chinese public mutual fund profile and NAV (公募基金档案与净值) in one call: official fund name,…
Chinese public mutual fund profile and NAV (公募基金档案与净值) in one call: official fund name, full legal name, fund company, custodian, managers, inception date, risk level, fund size, latest unit NAV with its date, period returns (1m/3m/6m/YTD/1y/3y/5y/since incep…
by CN Data · verified provider · updated 2026-11-04
What it does
Chinese public mutual fund profile and NAV (公募基金档案与净值) in one call: official fund name, full legal name, fund company, custodian, managers, inception date, risk level, fund size, latest unit NAV with its date, period returns (1m/3m/6m/YTD/1y/3y/5y/since inception) and the recent NAV history table with purchase/redemption status. Pass ?code=000001 (6-digit fund code) and optional ?history=0-60. Chinese funds publish NAV daily and investors cannot get this as clean JSON anywhere else. 中文:公募基金档案(公司、基金经理、风险等级、规模)+ 最新净值 + 各区间收益 + 历史净值。 No API key and no signup: call the endpoint, it answers HTTP 402 with the payment terms, pay per request in USDC on Base with any x402-compatible client or wallet, then retry the same request to get the data.
Tags: china · fund · mutual-fund · finance · nav · 基金
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/74981.jsonfor the price and payment options. - Pay. Call
GET https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/fund. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.02 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.02 | 0xE69507F3e6F57A63e90a638E59C47d1b48dc3229 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xE69507F3e6F57A63e90a638E59C47d1b48dc3229",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "20000",
"amountUsd": 0.02,
"maxTimeoutSeconds": 300
}
]Examples
curl "https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/fund"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/fund");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/fund")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- CN Data
- Endpoint
- https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/fund
- Machine-readable
/resources/74981.json