- Financial statements — income statement, balance sheet, cash flow. Quarterly and annual, normalized to a single canonical schema. See Financials.
- Segments — per-segment revenue, operating income, assets, and capex with per-segment time series. See Segments.
- Ownership — insider trades, institutional holdings, major shareholders, and director holdings. See Ownership.
- MCP server — same data exposed as 17 Model-Context-Protocol tools for Claude Desktop, Cursor, Cline, and other LLM clients. See MCP server.
Introduction
A cross-market financial data API. Historical statements and disclosures parsed directly from each market's XBRL filings.
Rockmoon covers three markets — US (SEC), JP (EDINET + TDnet), and KR (DART) — and normalizes them into one schema. Every value you read from the API is extracted directly from a specific XBRL fact in a specific filing.
There is no real-time price feed, no analyst estimates, no forward guidance — Rockmoon is what's in the filings, normalized and queryable.
What you can access
Quick start
Three steps. About sixty seconds.
1. Get an API key
Sign in at /login using Google OAuth or a one-time email link. A free-tier key is provisioned automatically. Find it on your dashboard.
2. Make your first call
Pass the key in the X-API-Key header. Try the
company-detail endpoint with AAPL — it's free-tier accessible
and works without quota.
curl -H "X-API-Key: rk_YOUR_KEY" \
https://api.rockmoon.ai/v1/company/AAPL
import requests
headers = {"X-API-Key": "rk_YOUR_KEY"}
r = requests.get("https://api.rockmoon.ai/v1/company/AAPL", headers=headers)
company = r.json()
print(company["name"], company["industry"])
const r = await fetch("https://api.rockmoon.ai/v1/company/AAPL", {
headers: { "X-API-Key": "rk_YOUR_KEY" }
});
const company = await r.json();
console.log(company.name, company.industry);
3. Read the per-section docs
Each API section in the sidebar has detailed per-endpoint documentation — parameters, response schema, edge cases, and per-market caveats. Start with Financials (the core) or jump to whatever your use case needs.
What's in this documentation
Reference
- Errors — uniform error shape, full list of
codeslugs - Pricing — Free / Basic quotas and rate limits
- Ticker format — alphabetic (US), 4-digit (JP), 6-digit (KR)
Endpoint sections
- Companies — cross-market search, company detail
- Financials — IS / BS / CF (combined or individual)
- Segments — per-segment IS / BS / CF + trend
- Ownership — insider, institutional, major shareholders, directors
- MCP server — same financial data over Model Context Protocol (Claude Desktop, IDE tools)
Conventions used in these docs
- Method + path are shown above every endpoint section. Path params are
{ticker}; query params come after?. - Required parameters are flagged in red in the params table. Anything else is optional with a documented default.
rk_YOUR_KEYin code samples is the literal placeholder text — replace with your key from /dashboard.