AmericanETP vs Refinitiv (LSEG) 2026

Buy a flat-priced constituent file subscription if the job is reconstructing index and ETF membership, weights and identifiers on a daily or point-in-time basis; buy from LSEG if the job needs real-time cross-asset pricing, corporate actions depth, news, research or a licensed benchmark. Those are different purchases, and most of the pages ranking for this comparison answer a question about terminals instead.

What the AmericanETP vs Refinitiv comparison is actually about

AmericanETP is a subscription CSV feed of daily updated ETF and index constituent lists, fundamentals and security identifiers. Refinitiv was a full financial data and analytics business, and its products are now delivered under the LSEG brand. These are not the same category of purchase, and treating them as rivals only makes sense if you narrow the question to one job.

That job is constituent acquisition: how does a firm get an accurate, dated list of what is inside an index or an ETF, with identifiers that join to the rest of its data, every trading day. Asked that way, the comparison becomes tractable. Asked as "which platform is better", it is unanswerable, because one of them is a file and the other is an institution.

The pricing asymmetry is worth stating before anything else. AmericanETP publishes its rates: $1,500 per year or $150 per month for an individual, $2,500 per year or $250 per month firm-wide. LSEG sells through enterprise agreements, and the pages read for this article do not publish a per-seat rate card, which means every LSEG figure circulating online is either a quote someone received or a third-party estimate.

The comparison pages that rank for this query, including Wall Street Prep's and Corporate Finance Institute's, both read on 12 September 2026, compare Refinitiv against Bloomberg, Capital IQ and FactSet and conclude on seat cost and analyst workflow. Useful if you are staffing a banking desk. Silent on whether a terminal relationship is the right way to buy constituent files at all.

Is Refinitiv now LSEG, and does the brand change affect buyers?

Yes. According to LSEG's own page on the change, as read on 12 September 2026, LSEG completed its acquisition of Refinitiv in 2021, the Refinitiv brand has since been fully retired, and former Refinitiv products and services are now delivered by LSEG Data & Analytics, FTSE Russell or LSEG Risk Intelligence.

For a data buyer, that reorganisation matters more than the logo. A constituent data requirement can land in any of the three lines depending on how it is framed: reference and pricing data sits with Data & Analytics, index membership for a licensed benchmark sits with FTSE Russell, and screening or entity risk work sits with Risk Intelligence. If you write "Refinitiv constituent data" into an RFP, you are asking a question that three different sales teams can answer differently.

The practical friction shows up in documentation. Internal data dictionaries, vendor mapping tables, contract schedules and old integration runbooks still say Refinitiv, and so do a great many third-party articles, because product names outlive brand retirements by years.

That lag is exactly why this comparison still ranks under the old name. Corporate Finance Institute's comparison page, read on 12 September 2026, still structures a section around "What is Refinitiv?" as a present-tense product. Nothing dishonest about that, but a buyer should expect the vendor's own materials and the internet's materials to use different vocabulary for the same thing.

Verdict on the brand question: it changes nothing about capability and everything about procurement. Search LSEG, not Refinitiv, when you want current terms.

Coverage: what each side actually delivers for index and ETF constituents

AmericanETP covers 3,878 US and global indexes and US-traded ETFs, with constituent lists updated twice daily: a primary update at 6pm EST and a secondary update at roughly noon EST. Holdings files carry Bloomberg FIGIs, a separate fundamentals file carries the ETF description, leverage and constituent counts, and archived constituent datafiles run back to July 2009.

The LSEG lineage covers a far wider surface. Cross-asset real-time pricing, reference data, corporate actions, news, research, analytics and, through FTSE Russell, index data as its own business line. None of that is attempted by a constituent file subscription, and pretending otherwise would be dishonest.

So the honest coverage statement is that LSEG wins breadth outright and AmericanETP wins on a single axis: the depth and consistency of constituent files as files, including the archive.

Verdict on coverage: if your requirement list includes anything beyond membership, weights, identifiers and fundamentals, AmericanETP will not be sufficient on its own. If your requirement list stops there, the rest of the LSEG estate is capability you are paying to have available rather than capability you are using.

Workflow: terminal and API versus flat files on FTP

The two products reach a model in fundamentally different shapes. AmericanETP delivers CSV files with the same schema every day, available over FTP or direct download, which means a loader, a cron entry and a schema check are the whole integration. The LSEG lineage delivers desktop workstation access alongside enterprise feed and API products, with entitlements, SDKs and a permissioning model built for large seat counts.

Neither shape is strictly better. They fail in different places, and the failure modes are what you should evaluate.

Where the file feed puts work on you

A flat file feed has no client library to learn and no entitlement mapping to maintain, but it also has no retry logic, no delivery guarantees you did not build, and no validation beyond what you write yourself. A serious file-based pipeline needs a checksum or row-count assertion, a diff against the prior day, and an alert when a file is late or a constituent count moves more than expected.

The upside is that every one of those components is yours, inspectable, and cheap to reason about at 7am when a number looks wrong. The Constituent Change Report covers part of the diffing problem directly, which reduces how much change detection you have to write.

Where the enterprise API puts work on you

An entitlement-managed API gives you permissioning, audit trails and a vendor to escalate to, which is not a small thing when the data underpins client reporting. The cost is integration: mapping entitlements to internal users, tracking which fields each contract permits, handling SDK version changes, and maintaining a vendor relationship that consumes someone's calendar.

That trade runs the same way against other enterprise platforms, and it is set out at more length in the AmericanETP vs FactSet comparison, where the workflow contrast is nearly identical.

Verdict on workflow: a team of two engineers who want data in a warehouse by Thursday should take the files. An organisation that must prove who accessed which field, across hundreds of seats, should take the entitlement layer and budget for the integration.

Cost: a published number versus a negotiated contract

AmericanETP's rates are public and flat: $1,500 per year or $150 per month for an individual, $2,500 per year or $250 per month firm-wide. That is the complete licence cost, and it does not change with how many indexes you pull or how often you pull them.

LSEG does not publish a public per-seat rate card on the pages read for this article on 12 September 2026. Wall Street Prep's comparison page, read the same day, does carry a dedicated section on what Refinitiv Eikon cost, and Corporate Finance Institute discusses budget as a selection criterion without publishing rates. Any specific 2026 LSEG figure you encounter, including in those pages, should be treated as a third-party estimate for a retired product name until you have it in a quote with your own name on it.

The more useful cost discussion is what sits outside the licence line. Three items dominate.

• Integration time. Engineering hours to first usable table, then hours per year to keep the connection healthy through SDK and schema changes.
• Entitlement administration. Someone owns the map from contracts to users to fields. On a flat file subscription that role does not exist; on an enterprise feed it is real work.
• Redistribution terms. Whether you may show the data to clients, embed it in a product, or store it after the contract ends. This is the clause that most often turns a cheap licence into an unusable one, and it is never visible from a marketing page.

We keep a longer breakdown of what is and is not sourceable on the LSEG side in Refinitiv pricing in 2026, including why estimates for the Eikon era should not be read as current LSEG rates.

Verdict on cost: if a published number you can budget against without a procurement cycle has value to you, that is a genuine and slightly unusual advantage of the file subscription. If your firm buys enterprise data anyway, marginal cost of adding scope to an existing LSEG agreement may beat a standalone subscription, and only a quote will tell you.

History and vendor risk: two very different institutions

AmericanETP was founded in the 1990s as MasterDATA and renamed to avoid confusion with IBM's use of the term, which makes it older than most current ETF data competitors. LSEG is an exchange group that assembled much of its data business by acquisition, which is precisely why the Refinitiv brand no longer exists.

Each history implies a different risk. A small, long-lived specialist carries concentration risk of its own kind: fewer product lines, a narrower surface, and no adjacent capability to grow into if your requirements expand. A large consolidator carries brand and product-line continuity risk, which the Refinitiv retirement demonstrates rather than refutes, plus the dependency that comes with single-vendor coverage across pricing, reference data and index licensing.

The archive question cuts across both. Reconstructing an index as of a past date requires point-in-time files that were written on that date, not a current list back-dated by reversing known changes. AmericanETP's archived constituent datafiles run back to July 2009, and that is the kind of asset that cannot be bought later: either the files were captured daily or they were not.

Verdict on vendor risk: buy LSEG if you want one counterparty accountable for a wide data estate. Buy the specialist if you want the narrow thing to keep working the same way for a decade, and check in writing how far each side's point-in-time history actually goes.

Which one fits which job in 2026

Here is the per-workflow verdict, stated without hedging.

Two of those rows are worth expanding, because they are the ones where a terminal purchase is most often made unnecessarily. An ETF list organised by sector is a job that a constituent feed completes on its own, with no pricing subscription involved. So is building an S&P 500 P/E ratio from constituents, which needs membership, weights and per-constituent fundamentals, and nothing else.

If you already hold an LSEG agreement and need only a sector breakdown or a membership history, adding scope there may still be the cheaper path. Check the incremental quote before assuming a second vendor is the answer.

How to run the evaluation yourself

Do not decide this from comparison articles, including this one. The test takes a data team under a week and produces an answer specific to your indexes rather than to somebody else's.

Pick five indexes and three ETFs whose composition you already know well enough to spot an error. On the same calendar date, pull constituents for all eight from every candidate, then compare four things: membership counts, the sum of weights, identifier coverage across the securities you care about, and the timestamp the vendor asserts for the file.

Then wait for a rebalance or reconstitution date and re-pull. Diff the before and after from each candidate against each other. A feed that gets membership right on a quiet Tuesday and lags on reconstitution day is not a feed you can backtest against, and this is the single test most evaluations skip.

Alongside the technical test, get two things in writing rather than inferring them from a marketing page: the redistribution terms, stated precisely enough to cover whatever you actually intend to do with the data, and the true depth of point-in-time history including whether historical files are the originals or reconstructions. Vendors answer both questions honestly when asked directly and vaguely when not asked.

The same procedure settles the adjacent comparisons without extra work, since the candidate list is just longer. It is the method behind both the AmericanETP vs ETF Global comparison and the AmericanETP vs Morningstar comparison, and if your identifier joins run through Bloomberg, the Bloomberg extensions documentation shows how the FIGI mapping is delivered.

FAQ

Is Refinitiv now called LSEG?

Yes. LSEG's own page on the change, read on 12 September 2026, states that LSEG completed its acquisition of Refinitiv in 2021, that the Refinitiv brand has been fully retired, and that former Refinitiv products and services are now delivered by LSEG Data & Analytics, FTSE Russell or LSEG Risk Intelligence. Documentation and third-party articles still using the Refinitiv name are describing products that now sit under one of those three LSEG brands.

How much does Refinitiv cost in 2026?

There is no published answer, because the Refinitiv brand no longer exists and LSEG does not publish a public per-seat rate card on the pages read on 12 September 2026. Wall Street Prep's comparison page carries a section on Eikon-era pricing, but that is a third-party estimate for a retired product and should not be read as a current LSEG rate. Pricing comes from a quote, and it varies with seat count, data scope and redistribution rights.

Is Refinitiv as good as Bloomberg?

The ranking comparison pages treat this as a workflow and coverage question rather than a quality ranking, and that is the right framing. Bloomberg's strength is messaging and desk-standard workflow; the LSEG estate is broad across reference data, risk and index businesses. For constituent data specifically, neither terminal is the natural purchase, because the deliverable you need is a file rather than a screen.

Is Reuters the same as Refinitiv?

They are related but not identical. Reuters is the news organisation, and its news content has long been distributed through the data business that became Refinitiv and then moved under LSEG. If you are buying news, you are buying a content licence; if you are buying constituent lists, the Reuters association is not relevant to the evaluation.

Can AmericanETP replace a Refinitiv or LSEG subscription?

Only if your requirement is genuinely limited to index and ETF constituent lists, weights, identifiers and ETF fundamentals. AmericanETP does not provide real-time quotes, corporate actions depth, news, research or index licensing rights, so it cannot replace an LSEG relationship built around those. It can, for many teams, remove the reason to buy a terminal seat purely to export holdings.

Does AmericanETP provide real-time data?

No. Constituent lists are updated twice daily, with a primary update at 6pm EST and a secondary update at roughly noon EST, delivered as CSV files. That cadence suits backtesting, screening, exposure analysis and product data pipelines. It does not suit intraday trading decisions that depend on live pricing.

Pull a sample constituent file, run the eight-security test described above against whatever you use today, and see whether the terminal line item is still doing work. Start at americanetp.com, or send your index list through the contact form and we will tell you plainly whether it is covered.