{
  "id": "p_FtGNV5zgtxaTN28h",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_FtGNV5zgtxaTN28h",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You run integrations for a regional restaurant group. Orders arrive from several delivery marketplaces, and someone on your team has asked a simple question: which of these companies can you actually build against? You open the Food Delivery page on apis.io and see 105 providers. It looks like a deep market.\n\nThe post you read says otherwise. The count is computed from tags rather than a fixed list, and it is mostly breadth. By the scores in each provider's own record, 57 of the 105 are minimal, 28 are emerging and 11 are thin. Five are developing, one is strong and two are exemplar. Only three companies clear 60 on the Kin Score, and the post says the market's integration surface runs through them.\n\nThose three are DoorDash at 76.2, Instacart at 70.0 and Grubhub at 60.1. The post also points out that food delivery is not one kind of API. It is at least four, and they score very differently. In marketplace and dispatch, Uber Eats sits at 46.9. In grocery and quick commerce, Getir is at 33.4. Kitchen operators are represented by CloudKitchens at 45.7, and rider networks by Barogo at 37.8. All of these scores come from the provider files, scored 2026-10-17.\n\nYour group takes orders from European marketplaces too, so the next finding lands close to home. The post says the US platforms published and the European ones mostly did not. Deliveroo is at 31.9, Just Eat at 34.5, Wolt at 38.0, Delivery Hero at 37.7 and Bolt at 26.8. These companies run large partner programs for restaurants and couriers, the post notes, yet the public, machine-readable side of those programs is thin. Only 11 of the 105 records list an MCP server.\n\nThere is a second surprise if you are thinking about automation. You might assume DoorDash is the safe bet for anything an agent does, since it leads the composite by 16 points. The post says otherwise. Grubhub's Agent Readiness is 48.4, against DoorDash's 37.6. A strong documentation surface and a contract an agent can safely act on are different things, and here they split.\n\nThen there is the part that speaks to your actual problem. Bevz scores 52.5 and Deliverart 50.1, and both land in developing, ahead of most of the platforms they aggregate. Both exist to consolidate orders from DoorDash, Uber Eats, Just Eat, Glovo and Deliveroo into one place. The post's reading is that the integration pain these marketplaces create is the product. For you, that means the middleware tier may be a better first look than five separate integrations.\n\nThe post then turns on its own catalog, and you should notice it. The industry page's member rows do not match the provider records. The page lists DoorDash with 49 APIs, while DoorDash's own record says 14 on a published basis. The 296 API header total is the sum of those row counts, so it inherits the same drift. The author cites the provider files rather than the page rows, and calls the mismatch a defect the catalog has to reconcile. So the number you first saw on that page is one you should treat with care, and the post says so about its own data.\n\nThe post's starting advice is short. If you are dispatching deliveries, start with DoorDash Drive. If you are integrating grocery, start with Instacart. If you are a restaurant receiving orders from many marketplaces, look at the middleware tier before building five integrations yourself. It adds that what would move the industry is the European marketplaces publishing contracts for the partner programs they already run.\n\nWhat you take away is a shorter list and a sharper question. Of 105 providers, three score above 60, and your decision should rest on the provider records rather than the page's row counts. For your group, that points to the middleware tier first, and to Grubhub if agent-safe actions matter more than documentation polish.\n\nRead the original: https://apis.io/2026/10/22/food-delivery-has-105-providers-and-three-that-score-above-sixty/",
  "title": "You Open the Food Delivery Page and Find 105 Providers, but Only Three Worth Building On",
  "topics": [
    "food-delivery",
    "api-scoring",
    "agent-readiness",
    "marketplaces"
  ],
  "published_at": "2026-10-22T13:41:13.381Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}