Food delivery has 105 providers on apis.io and three that score above sixty

Food delivery has 105 providers on apis.io and three that score above sixty

Food Delivery on apis.io counts 105 providers, computed from tags rather than a fixed list. That sounds like depth. It is mostly breadth. By the scores in each provider’s own record, 57 of the 105 are minimal, 28 emerging and 11 thin. Five are developing, one is strong, two are exemplar. Three companies clear 60 on the Kin Score, and the market’s integration surface runs through them.

The functional bands

Food delivery is not one kind of API. It is at least four, and they score very differently.

Band Provider Kin Score Agent Readiness
Marketplace and dispatch DoorDash 76.2 exemplar 37.6 agent-ready
Marketplace and dispatch Grubhub 60.1 strong 48.4 agent-ready
Marketplace and dispatch Uber Eats 46.9 developing 31.4 agent-ready
Grocery Instacart 70.0 exemplar 37.9 agent-ready
Grocery and quick commerce Getir 33.4 thin 31.8 agent-ready
Restaurant order middleware Bevz 52.5 developing 27.9 agent-aware
Restaurant order middleware Deliverart 50.1 developing 23.9 agent-aware
Kitchen operators CloudKitchens 45.7 developing 30.3 agent-ready
Rider networks Barogo 37.8 thin 37.9 agent-ready

All scores are from the provider files, scored 2026-10-17.

What the record shows

The US platforms published; the European ones mostly did not. DoorDash, Instacart and Grubhub are the only three above 60. Deliveroo sits at 31.9, Just Eat at 34.5, Wolt at 38.0, Delivery Hero at 37.7, Bolt at 26.8. These are companies with large partner programs for restaurants and couriers, and the public, machine-readable side of those programs is thin.

Grubhub has the best agent record in the industry, not DoorDash. Grubhub’s Agent Readiness of 48.4 beats DoorDash’s 37.6 even though DoorDash leads by 16 points on the composite. A strong documentation surface and a contract an agent can safely act on are different things, and here they split.

The middleware layer is where the small companies score. Bevz and Deliverart both exist to consolidate DoorDash, Uber Eats, Just Eat, Glovo and Deliveroo orders into one place, and both land in developing, ahead of most of the platforms they aggregate. The integration pain these marketplaces create is the product.

Only 11 of the 105 records list an MCP server.

A catalog note

The industry page’s member rows do not match the provider records. The page lists DoorDash with 49 APIs; 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. I cite the provider files here, not the page rows. That is our defect to reconcile.

Where to start

If you are dispatching deliveries, start with DoorDash Drive. If you are integrating grocery, Instacart. If you are a restaurant receiving orders from many marketplaces, look at the middleware tier before building five integrations yourself.

What would move the industry is the European marketplaces publishing contracts for the partner programs they already run. Browse the full list at apis.io/industries/food-delivery/.

← DynamoDB Transactions is two operations, and our contract for it drops seven of nine errors
Foreca says API documentation you'll love, and publishes no contract →