Methodology

GLP-1 Ledger republishes public government records: mainly FDA’s, plus state board of pharmacy files and Justice Department and state attorney general press releases. Every row links to the document it came from, and nothing is estimated, rated or filled in. The records were last pulled on Nov 15, 2026 and are refreshed weekly.

Sources

Justice Department and state attorney general records

The enforcement page lists 10 actions from official press releases: 1 from the Justice Department (justice.gov) and 9 from state attorneys general (Connecticut Attorney General, Alabama Attorney General). Each record keeps the release title and date, the action type in the release’s own words, and the release’s sentence naming the firm, quoted. Every weekly run re-reads each release and drops any record whose title, date or quoted sentence is no longer on the page. Lawsuits, charges, letters and investigative demands are labeled as allegations. A release counts only when it names semaglutide, tirzepatide, another GLP-1 drug or a GLP-1 brand name, and a firm (individuals named alone are not listed).

This index read every press release on justice.gov’s press release list dated Jan 1, 2026 to Nov 14, 2026 (18,139 releases read through the department’s public press release API) and found 9 releases naming semaglutide, tirzepatide, another GLP-1 drug or a GLP-1 brand name. justice.gov asks automated readers to wait 10 seconds between requests, and this index does. State attorney general releases were found by search and read on each office’s own site, so that list is not complete for every state.

A firm in these releases is shown on an existing company page only when the release states the same name (after the normalization above) or a website FDA named in a GLP-1 warning letter. Otherwise it gets its own page. Nothing is matched on a similar name.

Not read: Federal Trade Commission (ftc.gov cases and press releases), because the FTC website answered this index’s requests with an error page instead of the page requested, so FTC cases and press releases were not read; this index does not work around blocks (checked Nov 7, 2026); Justice Department press releases dated before January 1, 2026, because justice.gov’s release pages answer automated requests with a bot check, so releases are read only through the department’s press release API, which this index reads back to January 1, 2026; earlier releases found by search were not read (checked Nov 7, 2026); Ohio Attorney General, because the Ohio Attorney General’s website did not respond to this index’s requests (checked Nov 7, 2026).

Federal lawsuits (CourtListener)

Not loaded: the court records source could not be read on the last check. No lawsuit records are shown anywhere on this site until it is.

FDA import records (API supply)

The GLP-1 import records page reads two FDA import sources on accessdata.fda.gov, 30 seconds apart per request as the host’s robots.txt asks, last on Nov 15, 2026. First, Import Alert 66-80 (published Oct 9, 2026): its reason, guidance and charge are quoted verbatim, and its Green List is shown entry by entry as FDA prints it, with FDA’s redaction in place of each firm name. 12 drug import alerts (66-80, 66-41, 66-40, 66-66, 66-72, 66-78, 66-79, 66-57, 66-76, 54-16, 55-05, 99-34) are searched for the words semaglutide, tirzepatide, liraglutide, retatrutide and GLP-1; other alerts are not searched. Second, FDA’s Import Refusal Report bulk files (Jan 1, 2002 to Oct 30, 2026), plus FDA Data Dashboard rows not yet in a bulk file: a line is kept when FDA’s product code description names one of those words (717 lines). A line counts as an API or powder form only when its product code is one Import Alert 66-80 itself lists. Declared manufacturer names that do not read as a business (no legal suffix or business word, and not a listed brand manufacturer spelling) are dropped at ingest with their city and FEI, so private individuals are never named; their lines still count by date, country and product. 67 business names get a page, one per spelling and country as FDA wrote it. No page is made for brand-name drug makers entered as declared manufacturer (Eli Lilly, Novo Nordisk, AbbVie, AstraZeneca, Bristol-Myers Squibb, Elanco and other originators, by name), for names that stop at exactly 32 characters or end in a cut-off word (read as truncated in FDA’s file) or are mostly digits, or for business names that open with a personal first and last name (those names are not shown); all of these lines still count in the totals. A firm page links to a company page only on the exact normalized name, and to a pharmacy page only on the exact name (U.S. firms) or the same FEI number.

FDA NDC Directory listings

The NDC listings page reads FDA’s four NDC Directory download files from accessdata.fda.gov, 30 seconds apart, last on Nov 15, 2026: finished drugs, unfinished drugs, the compounded drugs file of outsourcing facility product reports, and the excluded drugs file of listings FDA removed or excluded. A row is kept when its substance, nonproprietary or proprietary name names semaglutide, tirzepatide, liraglutide, retatrutide or cagrilintide (467 listings); an excluded row with blank names is kept only when its application number is one a kept finished or unfinished listing carries. Fields, including the marketing category, are copied as FDA gives them; the compounded file’s package rows are grouped into one listing per product NDC. openFDA’s drug NDC endpoint is read for per-drug totals as a cross-check. FDA’s NDC Directory disclaimer is quoted verbatim and checked against FDA’s page on each run. A labeler is shown on a 503B facility, pharmacy, company or import records page only when its name, or a “dba” name in it, has the same normalized key as that page; the NDC files carry no FEI number or address, so no other match is made, and a firm with several locations shows the same listings on each. 26 labelers with 2 or more compounded or bulk ingredient listings and no other page get their own page; Novo Nordisk and Eli Lilly entities, approved-product labelers and further-processing labelers are listed without a page.

Medicare and Medicaid spending

The spending page reads two CMS sources, aggregate only: no prescriber, pharmacy or patient level file is read. First, CMS’s Medicare Part D Spending by Drug file (DSD_PTD_RY26_P04_V10_DY24_BGM.csv), 2020 to 2024, through the data.cms.gov data API, with requests spaced 10 seconds apart as that host’s robots.txt asks. Rows whose generic name contains “tide” are fetched and a row is kept only when CMS’s generic name is exactly one of Semaglutide, Tirzepatide, Liraglutide, Dulaglutide, Exenatide, Exenatide Microspheres, Lixisenatide, Insulin Glargine/Lixisenatide, Insulin Degludec/Liraglutide, using CMS’s “Overall” row for each brand. The Part B file is searched the same way for generic names containing glutide, xenatide, tirzepatide, lixisenatide, to record whether it has any GLP-1 row. CMS’s catalog sentences quoted on the pages are re-checked against data.cms.gov/data.json on each run.

Second, CMS’s Medicaid State Drug Utilization Data, one dataset per year from 2020 to 2026, through data.medicaid.gov’s datastore query API (product name starting with any of the names below, 8,000 rows a page, 5 seconds apart). CMS gives only the first 10 characters of the FDA listing name, so a row is kept when the first word of that name is exactly one of: OZEMPIC (Ozempic); WEGOVY (Wegovy); RYBELSUS (Rybelsus); SEMAGLUTID (Semaglutide (generic name listing)); MOUNJARO (Mounjaro); ZEPBOUND (Zepbound); TIRZEPATID (Tirzepatide (generic name listing)); VICTOZA (Victoza); SAXENDA (Saxenda); LIRAGLUTID (Liraglutide (generic name listing)); TRULICITY (Trulicity); TRULICITY0 (Trulicity); DULAGLUTID (Dulaglutide (generic name listing)); BYETTA (Byetta); BYDUREON (Bydureon); EXENATIDE (Exenatide (generic name listing)); ADLYXIN (Adlyxin); SOLIQUA (Soliqua); XULTOPHY (Xultophy). Rows are added up by state, year, quarter and product, fee-for-service and managed care together. A row CMS marks suppressed is counted as suppressed and its blank values are never treated as zero: a total that includes one is shown as “at least” the published sum, and a total of only suppressed rows is shown as “Suppressed.” National figures are the rows CMS files under the state code XX. As read on Nov 15, 2026: 2020, 5,073 rows (1,682 suppressed); 2021, 6,574 rows (2,143 suppressed); 2022, 8,243 rows (2,985 suppressed); 2023, 9,756 rows (3,101 suppressed); 2024, 10,631 rows (3,186 suppressed); 2025, 12,829 rows (4,096 suppressed); 2026, 3,454 rows (1,141 suppressed), quarters 1 posted.

Neither source nets out rebates, and neither says what a prescription was for. Retatrutide and cagrilintide are searched for in both; a drug page says a file has no product under a name only when that search ran.

How records are matched to companies

Company names are normalized (case, punctuation, suffixes such as Inc. and LLC, and anything after “dba”) and records are joined on that key. So “FitRX, LLC dba Zealthy” and “FitRX, LLC dba AM RX” appear on one company page, with every name FDA used listed there. A company page exists only when a warning letter or recall names a GLP-1 ingredient; being on FDA’s 503B list alone does not create one, because that list does not say what a facility makes.

Each facility on FDA’s 503B list has its own page. It is matched to its entry on FDA’s compounding actions page when both are 503B, in the same city and state, and their legal or dba names share the same normalized key or the same first distinctive word (for example “Olympia Pharmaceuticals” and “OPS International, Inc. (dba Olympia Pharmacy)”, both in Orlando, Florida). If two entries could match, none is shown. Company pages show compounding action entries whose legal or dba name has the same normalized key as the company. Pages that gather records under a shared name, such as the Empower, Olympia and Strive question pages, say plainly that the records do not show how the named entities are related.

Each pharmacy page (under pharmacies by state) gathers the entries on FDA’s compounding actions page and the rows on FDA’s 503B list for one pharmacy. Records are merged only when a legal or dba name has the same normalized key and the city and state are the same (“St.” and “Saint”, “Mt.” and “Mount” count as one city). A name FDA gives as “formerly” is a different legal entity and is never used to merge. Records that come close but fail the rule, such as the looser first-word match used on the 503B facility pages, stay on separate pages and are listed on each as a close but not exact match. When FDA lists the same letter under a firm’s 503A and 503B entries, it is counted once. Every pharmacy answer uses one of four forms: record found, with the source and date; no matching record found in a named source on a date; not checked, with the reason; or no match possible, when FDA gives nothing to match on.

“Type” on a company page repeats a label in an FDA subject line (for example “(Telehealth)” or “(Internet Pharmacy)”) or the company’s presence on FDA’s 503B list. Subject groups on the letters page restate FDA’s subject line; FDA’s exact wording is always shown.

FDA inspection classifications

The FDA Data Dashboard identifies each inspected site by an FEI number, which neither FDA’s 503B list nor its compounding actions page prints. A dashboard site is tied to a pharmacy page only when its legal name has the same normalized key as one of the page’s FDA names and its city and state are the page’s. The site’s inspections are then read by its FEI number, keeping those listed under the matched name, and its published Form 483s by FEI number alone. A site with the same name and state in another city is shown on the page as close but not exact, never as its record. Each inspection shows FDA’s classification as the dashboard words it (No Action Indicated, Voluntary Action Indicated or Official Action Indicated) with its end date and project area. The dashboard lists inspections once FDA has classified them, from fiscal year 2009 on, and FDA publishes only some Form 483s, so a missing inspection or 483 is reported only as not found in the dashboard on the date checked.

Form 483 observations

FDA publishes Form 483s (inspectional observations) as PDF links in three places this index reads: under each facility on its compounding inspections and actions page (some of those links point to an Internet Archive copy, which FDA itself links when it has removed the file), in the “Form 483 Issued?” column of its 503B list, and in the FDA Data Dashboard by FEI number. Every such link for a pharmacy or outsourcing facility with a page here is downloaded once (734 PDFs as of Nov 15, 2026), at least 30 seconds apart on fda.gov as its robots.txt asks.

A PDF is shown on a page only when its cover matches the page: the cover’s FEI number is one the FDA Data Dashboard ties to that page (see above), or the firm name on the cover (either side of a “dba”) has the same normalized key as one of the page’s names and the cover’s city and state are the page’s. Where FDA lists one firm under two entries that this index keeps on separate pages, a 483 that matches both is shown on both. The observations are read from the PDF’s text, in the order and with the numbers FDA printed. A 483 is skipped, and counted, when it or any of its pages has no text layer (a scanned image without one), when its observation numbers do not run 1, 2, 3 without a gap (a misread heading), when more than 2% of its words look like character-recognition noise, or when its cover matches no page. As of Nov 15, 2026: 476 shown, 39 with no readable text, 127 with observations that could not be read reliably, 80 matching no page, 1 not downloaded.

Text is quoted as extracted, with spacing tidied. FDA’s en and em dashes are written as hyphens, and FDA’s redaction markers (such as “(b)(4)” or “<Redacted B4>”) are kept. Some 483s are scanned images with a character-recognition text layer; those are marked on the page because that layer can misread characters. Names of people on the cover and in the signature box (the person the form was issued to and the investigators) are never stored, and any of those names, or a name after “Mr.”, “Ms.”, “Mrs.”, “Dr.” or “Miss”, found in an observation is replaced with “Name not shown”. Firm names and addresses are shown. The district office is the address printed in the form’s “District address” box, without phone numbers.

Themes on the 483 pages are counted with a fixed keyword table, printed on the answer page, applied only to each observation’s one-line lead statement. A 483 is not a final FDA determination, and a theme count is not a finding by this site.

State board records

For California, Colorado, Connecticut, Delaware, Florida, Illinois, Michigan and Texas, each pharmacy page is checked against the state board of pharmacy’s own public file. A board row is tied to a pharmacy only when a name on the row has the same normalized key as one of the pharmacy’s FDA names, and the row’s city and state are the pharmacy’s. A street address is never used to add or drop a match. Rows that come close (same name in another city, or a longer form of the name in the same city) are listed on the page as close but not exact, never as its license. Nonresident licenses another checked board issued count only when the board row names the pharmacy’s own city and state. When no row matches, the page says no license with that exact name and city was found in the file of that date, because a pharmacy can hold its license under a different legal name; that is not a finding that it is unlicensed. Board actions are quoted in the board’s words and are not characterized.

For Maryland, New York, Tennessee and Virginia, this index reads the board’s published disciplinary actions but not its license records, so the license answer on those pages says license records are not checked, with the reason. Each action is tied to a pharmacy page by the same rule: a name on the action has the same normalized key as one of the pharmacy’s FDA names, and the city and state given with the action are the pharmacy’s. An action that names another state’s address can only match a pharmacy page in that state, where it is shown as a board action in another state. When no action matches, the page says no action under that exact name and city was found in that list over the dates it covers.

Not checked: Alabama, because the Board of Pharmacy sends its license roster only by email, after the requester agrees to terms that limit how the data may be used, and its license verification is an interactive search; Arizona, because the board’s website, which hosts its license verification and board orders, answers automated requests with a bot challenge, and this index does not work around blocks; Arkansas, because the board’s license verification site answered automated requests with a firewall block, and this index does not work around blocks; no license file was found on the board’s website when checked on November 10, 2026; Georgia, because no license file or list of board orders was found on the board’s website when checked on November 10, 2026; its license verification is an interactive search; Idaho, because the board’s former web address (bop.idaho.gov) did not respond on November 6, 2026, and no longer resolved when tried again on November 7, 2026; the board’s pages now sit on the Division of Occupational and Professional Licenses site, which this index has not yet read; Indiana, because the Professional Licensing Agency sells its license files rather than publishing them, and its discipline records are behind an interactive search; Kansas, because the board’s website answers automated requests with a bot challenge, and this index does not work around blocks; Kentucky, because the board releases its license rosters only on request, and its board actions page shows nothing without running scripts; Louisiana, because no license file or list of board actions was found on the board’s website when checked on November 10, 2026; its credential verification is an interactive search; Massachusetts, because the board’s website refused automated requests, and this index does not work around blocks; Minnesota, because the board’s website answers automated requests with a bot challenge, and this index does not work around blocks; Mississippi, because the Board of Pharmacy sends its license roster only by email, after the requester agrees to terms that limit how the data may be used, and its license verification is an interactive search; Missouri, because the Division of Professional Registration’s license downloads sit on a script-driven portal, and its robots.txt file disallows the board’s pharmacy pages; Nevada, because no license file or list of board actions was found on the board’s website when checked on November 10, 2026 (it takes requests for discipline records); its license verification is an interactive search; New Jersey, because the Division of Consumer Affairs website, which publishes pharmacy permit records and board actions, answers automated requests with a bot challenge, and the state’s public license lookup lists individual licensees but not pharmacy permits; this index does not work around blocks; North Carolina, because the board’s website refused automated requests with an access error, and this index does not work around blocks; Ohio, because the board’s website rejected automated requests and the state’s eLicense lookup answers them with a script check, and this index does not work around blocks; Oklahoma, because no license file or list of board actions was found on the board’s website when checked on November 10, 2026; its license lookup is an interactive search; Oregon, because the board lists 2025 and 2026 actions in a script-driven table and older actions only on request, and its license lookup is an interactive search; Pennsylvania, because the Department of State’s license lookup (PALS) did not respond on November 6, 2026, and when tried again on November 7, 2026 it answered with a script-driven search application, which this index does not use; its monthly discipline reports are listed only through a script-driven search page; South Carolina, because the Department of Labor, Licensing and Regulation’s board website did not respond to this index’s requests on November 6, 2026, or when tried again on November 7, 2026; Utah, because the Division of Professional Licensing’s website refused automated requests, and this index does not work around blocks; Washington, because the Department of Health’s open dataset on data.wa.gov lists individual credentials but not pharmacy licenses, and its enforcement column has been removed for now; the department’s provider search is an interactive search, which this index does not use; Wisconsin, because the Department of Safety and Professional Services shows orders only through a script-driven search behind a user agreement, and its license lookup is an interactive search; Alaska, Hawaii, Maine, Montana, Nebraska, New Hampshire, Puerto Rico, Rhode Island, South Dakota, Vermont, West Virginia, because this index has not yet added those boards’ records. Florida’s export gives no state for nonresident permits, so Florida nonresident licenses held by pharmacies in other states are not checked. Texas license detail pages and California’s per-license detail pages are not fetched, because the boards’ robots.txt files disallow them. The New York Office of the Professions’ list pages and Tennessee’s monthly reports are fetched at most once a week, with past years kept longer, and both sites’ robots.txt files allow them. Illinois, Connecticut and Delaware licenses (and Delaware’s discipline) are read from the states’ open-data portals (data.illinois.gov, data.ct.gov and data.delaware.gov) through the portals’ published query endpoints, with a pause between requests as their robots.txt files ask. Michigan’s list is the Pharmacy group report that LARA’s licensing system generates as a spreadsheet, with no login, and that LARA’s License Lists and Reports page links; that page refused this index’s automated requests, so the report is opened directly, once a week, at https://aca-prod.accela.com/MILARA/Report/ShowReport.aspx?module=Licenses&reportID=32414&reportType=LINK_REPORT_LIST (the same report anyone can open from LARA’s page, without an account). The report host, aca-prod.accela.com, publishes no robots.txt file (checked November 11, 2026), so it sets no crawl limits. It lists active licenses only. Virginia’s list covers only case decisions entered in the last 90 days, so a Virginia pharmacy page with no matching action says so for that window only. Maryland’s Board of Pharmacy lists its orders by name and date and gives the city only inside each PDF, so every order not labeled with a person’s surname and initials is downloaded, about two seconds apart, and read; robots.txt on health.maryland.gov allows the order files. The city comes from the respondent’s address block or a sentence placing it (“located in Hagerstown, Maryland”). Orders whose PDF is a scan with no text, or whose text gives no city, cannot be matched and are not shown on any pharmacy page, because a name alone does not tie an order to a pharmacy. Boards looked at between Nov 6, 2026 and Nov 10, 2026 and not read: Alabama, Arkansas, Arizona, Georgia, Iowa, Idaho, Indiana, Kansas, Kentucky, Louisiana, Massachusetts, Minnesota, Missouri, Mississippi, North Carolina, New Jersey, New Mexico, Nevada, Ohio, Oklahoma, Oregon, Pennsylvania, South Carolina, Utah, Washington and Wisconsin, for the reasons above, and, for states with no pharmacy page here, Iowa, because no license file was found on the board’s website when checked on November 10, 2026, and its license lookup and board action search are interactive searches; New Mexico, because the Regulation and Licensing Department lists Board of Pharmacy actions in a script-driven table, and its license verification is an interactive search.

What is excluded

Limits

Updates and corrections

The ingest runs weekly and replaces each data file only when its source downloads and validates. If a record here differs from the FDA original, the FDA original is correct; the fix is made at the next run.

Last run notes: 3 source issue(s) recorded; the previous data was kept for those sources.