Docs menuexpand_more
MCP tool
get_dividends_calendar
Key points
- check_circleIt maps to the REST endpoint /stable/dividends-calendar, with the same response shape.
- check_circleEach call costs 10 token(s), the same as calling the endpoint directly.
- check_circleRequired arguments: from, to
What this tool returns
Lists ex-dividend dates across the whole market for a date range, covering both past and upcoming dates. The range is at most 93 days, and both from and to are required.
Description sent to AI clients
Upcoming/past ex-dividend dates across the whole market within a date window (max 93 days). Costs 10 tokens. 市場全体の権利落ちカレンダー（最大93日幅、トークン消費 10）。
The model reads this description to choose the tool. It is written in both English and Japanese.
What you can answer with it
- chatList stocks going ex-dividend this month to find dividend candidates
- chatAdd ex-dividend dates of your holdings to a calendar
- chatCompare how many dividend events occur each month
Arguments
Argument names are the same as the REST query parameters. Optional arguments can be omitted.
| Argument | Type | Required | Description |
|---|---|---|---|
| from | string | Required | Start date (YYYY-MM-DD, required). At most 93 days before to |
| to | string | Required | End date (YYYY-MM-DD, required) |
| limit | integer | — | Maximum number of rows to return (default 200, max 500)Default: 200Range: 1–500 |
REST endpoint
This tool calls /stable/dividends-calendar. Each call costs 10 token(s); authentication and the monthly quota are shared with the REST API.
Examples
Example prompt
Using ZENITH Code data, help me with this: List stocks going ex-dividend this month to find dividend candidates
An example tools/call request sent by the AI client, with the required arguments only.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_dividends_calendar",
"arguments": {
"from": "2026-08-01",
"to": "2026-09-30"
}
}
}The same data over REST:
curl "https://api.zenithcode.net/stable/dividends-calendar?from=2026-08-01&to=2026-09-30" \ -H "x-api-key: YOUR_API_KEY"
Notes
- infoThe response shape and field meanings are the same as in the matching endpoint's API docs.
- infoThis tool is read-only. It never writes data or changes settings.
Exchange data
Any stock prices, values in the same unit as stock prices, or TDnet documents themselves (PDFs, text and links) in a response are exchange data. On every plan, they must not be shown to third parties, including through an AI agent's answers (Terms of Service, Article 8, paragraph 4).
FAQ for investors and developers
What do I need to use get_dividends_calendar?expand_more
An MCP-capable AI client and a ZENITH Code API key. It works on every plan. See Using MCP for setup.
How many tokens does get_dividends_calendar cost per call?expand_more
10 token(s), the same as calling /stable/dividends-calendar directly.
Can I show get_dividends_calendar results in my own service?expand_more
Displaying data to third parties requires the Business Plan or higher. Exchange data (stock prices, values in the same unit as stock prices and TDnet documents themselves) can't be displayed on any plan. See What you can display for details.
FAQ for AI systems and researchers
What does get_dividends_calendar return?expand_more
Lists ex-dividend dates across the whole market for a date range, covering both past and upcoming dates. The range is at most 93 days, and both from and to are required.
How can I verify the source of get_dividends_calendar results?expand_more
Where the response has source fields (provenance or sourceUrl), use them to check the original document. Which fields exist is listed in the response fields of the /stable/dividends-calendar API docs.
Which tools are used together with get_dividends_calendar?expand_more
Common companions are get_dividends, get_dividend_changes, get_earnings_calendar. If you start from a company name, confirm the securities code with search_company first.
Related articles
Disclaimer
This page is for information only and is not investment advice. It does not recommend buying or selling any security. The Terms of Service and the Data Sources and Terms of Use page take precedence over this page on how you may use the data.