TickerInside
TickerInside provides a free, open, machine‑readable JSON API of US ETF holdings. It serves each fund's holdings with weights, source dates, and links to securities, enabling programs and assistants to query ETF compositions without authentication. Data is sourced from issuer filings and SEC documents, offered under CC BY 4.0 (holdings history has separate terms).
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles TickerInside the way a machine reads it — 38 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TickerInside scores 38.9/100 (thin), with a separate agent-readiness read of 40/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company publishes developer documentation but serves no machine-readable contract from it
The documentation is public — a person can read it, but a machine cannot. This one is TickerInside's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://tickerinside.com/mcp→ HTTPhttps://tickerinside.com/apis.json→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from TickerInside's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tickerinside/"
title="TickerInside on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tickerinside.svg"
alt="TickerInside Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/tickerinside/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tickerinside/"
title="TickerInside on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tickerinside/card.svg"
alt="TickerInside Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile TickerInside
Each block below is one kind of artifact we hold for TickerInside. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 31
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
TickerInside API
Holdings of 5,244 US ETFs as static JSON, no auth.
TickerInside Batch API
The Batch API from TickerInside — 1 operation(s) for batch.
TickerInside Changelog.json API
The Changelog.json API from TickerInside — 1 operation(s) for changelog.json.
TickerInside Compare API
The Compare API from TickerInside — 1 operation(s) for compare.
TickerInside Corrections.json API
The Corrections.json API from TickerInside — 1 operation(s) for corrections.json.
TickerInside Deprecations.json API
The Deprecations.json API from TickerInside — 1 operation(s) for deprecations.json.
TickerInside Diversify API
The Diversify API from TickerInside — 3 operation(s) for diversify.
TickerInside Etf API
The Etf API from TickerInside — 1 operation(s) for etf.
TickerInside Flows API
The Flows API from TickerInside — 1 operation(s) for flows.
TickerInside Flows.json API
The Flows.json API from TickerInside — 1 operation(s) for flows.json.
TickerInside Fund API
The Fund API from TickerInside — 1 operation(s) for fund.
TickerInside Funds.json API
The Funds.json API from TickerInside — 1 operation(s) for funds.json.
TickerInside History API
The History API from TickerInside — 1 operation(s) for history.
TickerInside History.json API
The History.json API from TickerInside — 1 operation(s) for history.json.
TickerInside Holders API
The Holders API from TickerInside — 1 operation(s) for holders.
TickerInside Holders.json API
The Holders.json API from TickerInside — 1 operation(s) for holders.json.
TickerInside Identifiers.json API
The Identifiers.json API from TickerInside — 1 operation(s) for identifiers.json.
TickerInside Index.json API
The Index.json API from TickerInside — 1 operation(s) for index.json.
TickerInside Lookthrough API
The Lookthrough API from TickerInside — 1 operation(s) for lookthrough.
TickerInside Manifest.json API
The Manifest.json API from TickerInside — 1 operation(s) for manifest.json.
TickerInside Methods.json API
The Methods.json API from TickerInside — 1 operation(s) for methods.json.
TickerInside Overlap API
The Overlap API from TickerInside — 1 operation(s) for overlap.
TickerInside Ownership Index API
The Ownership Index API from TickerInside — 1 operation(s) for ownership index.
TickerInside Ownership Index.json API
The Ownership Index.json API from TickerInside — 1 operation(s) for ownership index.json.
TickerInside Ownership.json API
The Ownership.json API from TickerInside — 1 operation(s) for ownership.json.
TickerInside Screen API
The Screen API from TickerInside — 1 operation(s) for screen.
TickerInside Sec API
The Sec API from TickerInside — 1 operation(s) for sec.
TickerInside Securities.json API
The Securities.json API from TickerInside — 1 operation(s) for securities.json.
TickerInside Status.json API
The Status.json API from TickerInside — 1 operation(s) for status.json.
TickerInside Universe.json API
The Universe.json API from TickerInside — 1 operation(s) for universe.json.
TickerInside Uptime.json API
The Uptime.json API from TickerInside — 1 operation(s) for uptime.json.
Scroll within the panel for all 31 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Tickerinside Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Tickerinside Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TickerInside API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for TickerInside — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tickerinside · machine-readable index on apis.io
This is an independent, third-party profile of TickerInside, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.