{
  "id": "p_djgNS9RSTnhd-N28",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_djgNS9RSTnhd-N28",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You have a routing project on your desk. Pickups, containers, invoices: the operational data a hauler runs on. You open the Waste Management vertical on apis.io expecting a field of options, and the page opens with a number that looks like depth: 33 providers publishing 278 APIs.\n\nThen you look at who supplies them. AMCS Group, an enterprise cloud software provider for waste, recycling and resource businesses, accounts for 257 of the 278 by itself. The other 32 providers share the remaining 21. And 27 of the 33 list zero APIs. Membership here is computed from catalog tags, not a hand-picked list, so the page shows where tagged providers actually stand.\n\nThe scores tell the same story. No provider in the vertical reaches the strong band. The best score, 46.2 and Developing, belongs to AMCS, the software vendor that sells to haulers, not to a hauler. Clean Harbors and Waste Management sit in Thin at 36.1 and 32.0, with 4 and 7 APIs. WM, Waste Connections and Stericycle are Emerging at 25.4, 14.7 and 14.6. Greyparrot, Republic Services and Veolia are Minimal at 12.1, 6.4 and 3.2, each with no APIs.\n\nThat is the first thing the page shows you: the haulers do not publish. Republic Services, one of the largest non-hazardous solid waste companies, scores 6.4 with no APIs. Veolia, which its own entry calls the global leader in environmental services, scores 3.2. Waste Connections, the third-largest North American provider by its description, has one API. The operational data in this industry reaches developers through vendors like AMCS rather than from the operators.\n\nThe second thing is about the sorting technology you may have been reading about. Greyparrot, AMP Robotics, Recycleye and EverestLabs all build computer vision for materials recovery facilities. None lists an API. Their product is analytics about what moves on a conveyor, and right now none of them exposes that data to anyone outside the facility. Two other members, AgriProtein and Fulcrum BioEnergy, score 0.0, and their own entries describe both in the past tense.\n\nHere is where the post turns on its own record, and it is worth your attention before you quote the 33. Waste Management (32.0, 7 APIs) and WM (25.4, 8 APIs) are both described as North America's largest environmental services company, and WM's entry notes it was formerly Waste Management, Inc. Fazla Gida and Whole Surplus are also one Turkish company, and each entry says so. So the 33-provider count includes at least two duplicates, and the two WM entries split 15 APIs that belong in one profile. The post is plain about whose fault that is: this is the catalog's cleanup to do, not the companies'. The page is accurate that the vertical is mostly one vendor's catalog, but it overstates the field by counting two companies twice.\n\nSo you adjust how you read it. If your project is integrating with waste operations, you start with AMCS Group, because its 257 APIs are where the sector's operating data lives. If your work touches hazardous and industrial services, Clean Harbors has four. If you need the largest US hauler, you read both WM entries until they are merged, and you treat their 15 APIs as one surface.\n\nWhat you take away is a habit of reading the denominator. A headline of 278 APIs across 33 providers suggests a broad market. The detail says one software vendor, a handful of thin entries, a long tail of silence, and a couple of duplicates the catalog still owes you a fix for. When the operators will not publish, the vendor in the middle is the integration, and the count you started with was smaller than it looked.\n\nRead the original: https://apis.io/2026/11/10/waste-management-lists-278-apis-and-257-of-them-belong-to-one-software-vendor/",
  "title": "You're integrating with waste operations, and the catalog hands you one vendor",
  "topics": [
    "waste-management",
    "api-catalog",
    "data-quality",
    "vendor-concentration"
  ],
  "published_at": "2026-11-10T18:29:42.637Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}