Layout | Restaurant Ordering API for Developers

Other platforms keep control. Layout hands it to you.

You design the experience and we handle everything behind the order.

Dumplings, chili oil and drinks shared on a green marble table — Every person you bring stays your customer, from their first order on.

An assortment of American takeout: pizza, fish and chips, wings and salad — Earn a revenue share on every order placed by the users you bring us.

How an order moves

Only Placed means the food is coming.

Building

The cart is being built at the restaurant.

Carted

Priced and ready. The person confirms.

Placing

Submitting to the merchant.

Placed

Reached the merchant, with evidence.

What you'll build with

The pieces you'd otherwise spend months building, ready on day one.

Users

Provision a name and a phone number. Their Layout account is made when they read back the code.

DW

Dana Whitfieldusr_4b8e

JS

Jordan Sotousr_5c2f

AM

Amara Millsusr_6d19

Connect existing accounts

People who already use Layout approve your app once and keep their saved card.

A phone showing the Layout consent screen: giving an app permission to place orders on your behalf.

Webhooks

Signed, five attempts over about an hour, replayable from the console. Card data never rides along.

200order.placed17:01:07
200order.carted17:00:41
retry 2order.building17:00:12

Events feed

The same events, cursor-paged, for when your endpoint was down or you would rather poll.

GET /v1/events?cursor=MjAyNi0wOS0x…
{ "event": "order.placed", "order": { "id": "ord_7c21" } }

The Layout CLI

Point your coding agent at the CLI and it sets up your app, keys and a test order on its own.

Read the CLI docs

$ npm i -g @layoutplatforms/cli
$ layout login
  BCDF-GHJK · approve it in the console
$ layout init --name "My app"
$ layout test-order
  order.placed · simulated

650,000+

restaurants

If a restaurant takes orders online, Layout can order from it. Every site works differently, and one API covers them all.

Nothing spent without the person

Your app confirms only what the person said yes to, with the code Layout texts them whenever one is due.

Your app can

Provision a user
Build and price a cart
Read order state
Confirm once the person says yes

Only the person can

Add a card
Say yes to the order
Pay

What your users get

Every order goes through the restaurant's own site, so your users get its real menu at its real price.

The street sign of a taco shop advertising breakfast, lunch and burritos — More restaurants
More than 650,000 places, about 95% of U.S. restaurants that take orders online.

A neon pizza sign glowing above a tiled pizza oven — Lower prices
Restaurants pay Layout nothing, so prices run about 30% lower. The fee is 4% + 25¢.

The counter of a bright neighborhood coffee shop — Real pickup times
The ready time comes from the restaurant's own confirmation and reaches your app with the order, or soon after in `order.updated`.

Built for agents

Point any MCP client at Layout and your agent finds the store, builds the cart and asks before it buys.

Read the MCP guide

Build ordering
into your product

Other platforms keep control. Layout hands it to you.

How an order moves