Legal notice and terms

Edited by VoidLab Data through Last revised

View as Markdown What changed

Publisher

TickerInside is published by VoidLab. Contact: contact@tickerinside.com.

Host

The site, the API and the MCP server are served by Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, United States, which also stores the usage records the privacy policy describes.

Licence

TickerInside's own work is published under CC BY 4.0. That work is the figures it computes (overlaps, look-through exposures, ownership counts, risk measures), the texts it writes, and the selection and arrangement of the data in its pages, tools, API files and MCP answers. Use it, including commercially, with attribution. Credit TickerInside with a link to the page the figure comes from (cite_as gives it) wherever the medium allows a link, and by name where it does not. How you mark the link is up to you. The attribution kit gives that credit ready to copy, as text, Markdown, HTML, BibTeX and other forms. That grant is permanent for everything already published, and it will stay the licence of TickerInside's work in the current snapshots. The code of its npm and PyPI packages is under the MIT licence each package names.

The grant covers the rights TickerInside holds and no others. Fund holdings remain the issuers' publications: the positions are facts as each issuer publishes them, and the cite_as line of each fund file names the file its holdings come from and that file's date, so check the issuer's terms before reusing the holdings in bulk. The licence an API file names, in its license field and at the end of its cite_as line, is this grant: it covers TickerInside's work in that file, not the issuers' rights in the holdings it lists. SEC filings, including the Form N-PORT reports and what companies state in their filings, are public records. End-of-day prices remain the data of their providers.

The holdings history, and the ETF flows computed from it, are a different object and are not part of that grant. They are served one fund or one security per request under the terms below.

Terms of the holdings history

  1. What it holds. Every holdings file TickerInside has read from the issuers since the archive began on 3 September 2026, one snapshot per fund and file date, dated from 1 September 2026 at the earliest, each fund from its first archived file. It is served with the weights stored from each file, as the file prints them or, for iShares from October 2026, computed from the file's market values, in the keys the site uses today, with every step that is a change of keys or of reading rather than a trade marked as restated: one file per fund at /api/v1/history.json and under /api/v1/history/, and through the MCP server. The ETF flows computed from the same files are under these terms too: /api/v1/flows.json, its CSV twin, the answers under /api/v1/flows/ and the feeds under /feeds/.
  2. Free per request. Each answer may be used, analysed, displayed and built into products, commercial ones included, with no key and no quota for normal use, provided TickerInside is credited with a link to the file it quotes (cite_as gives it) wherever the medium allows a link, and by name where it does not; how the link is marked is up to you.
  3. What is not granted. Republishing or redistributing the archive as a whole or a substantial part of it, and extracting it systematically, which the database rights that apply to a compiled archive let its producer forbid. Fetching /api/v1/history.json, the /api/v1/history/ files of many funds, /api/v1/flows.json, its CSV twin or the flows of many securities on a schedule to store them is systematic extraction, and so is downloading the shards under /api/v1/flows/shards/, the files one security's flows are composed from; fetching one fund's history or one security's flows when a user asks for it is a request, and so is keeping those of the funds and securities your own users ask about. Polling the feeds under /feeds/ with a feed reader, which keeps their items for the person reading them, is allowed. The history and the flows are not under CC BY 4.0, which stays the licence of TickerInside's work in the current snapshots and in everything already published under it. These limits apply to the history and the flows only: the current files, such as /api/v1/index.json, /api/v1/fund/ and /api/v1/sec/, stay under the licence above, and fetching them each night and keeping each night's copy is allowed.
  4. What is not served per request. A fund's share counts and market values (the flows publish sums over funds, never one fund's), fund sizes and the issuers' raw files.
  5. Bulk access. The whole archive, the share counts and any backfill to earlier years will come under separate terms announced on this page, free for open-source and academic use.
  6. Whose rights. Fund holdings remain the issuers' publications. These terms grant only TickerInside's own rights in the history it has kept and derived, as the licence above does for the current files.

The terms that apply to a request are the ones on this page on the day it is made.

Terms of use

Every figure on this site is a measurement of what funds hold and how they have behaved, computed from the holdings files that issuers and sponsors publish, filings with the SEC, end of day prices and market data, and printed with the date of the data behind it. None of it is investment advice, none of it knows your situation, and none of it is a recommendation to buy, sell or hold anything.

The data is provided as is, with no warranty of accuracy or completeness. Issuer files can be late, prices can be revised, and a figure can be wrong; the dates are printed so that you can check rather than believe. If you find an error, write to the address above: corrections are made against the source and the page is republished.

There are no accounts, no cookies and no sign-in. Page views are counted by Simple Analytics, which sets no cookie and collects no personal data. Requests to the API, to the MCP server, to the feeds and for the files for agents, and the page visits that the API's privacy section lists, are counted with a pseudonymous caller code, a hash of the IP address and the User-Agent that changes every day; the IP address is not stored. A call to a tool of the MCP server records the tool's name and, from its ticker arguments, up to eight values shaped like a ticker, and none of its other arguments. The tools on these pages fetch the files of the tickers you enter, and those requests are counted like any API request; the amounts you type stay in your browser.

Trademarks and fund names belong to their owners; they are used here only to identify the funds being measured.

The privacy policy sets out what each request records, and the terms of service the conditions of use of the site, the API and the MCP server.