Build ordering
into your product.
Real pickup orders at essentially any restaurant, through one MCP.
Layout can order at ~95% of restaurants in the U.S. that support online ordering.
No coverage list to maintain, no merchant to onboard. Layout drives each restaurant's own ordering site, the same one a person would use.
Connect once, order anywhere.
{ "mcpServers": { "layout": { "url": "https://mcp.layout.link" } } }
-
Any MCP client
The same connector people already use in Claude and ChatGPT, driven by your product instead of a chat window.
-
Essentially any restaurant
Layout drives the restaurant's own ordering site. No menu to sync, no merchant to onboard, no coverage list to check.
-
Priced before it is paid
The cart is read back from the checkout itself, so the total your user confirms is the total the restaurant charges.
-
One card, then never again
Your user saves a card once, at sign-up. Every order after that goes through with no payment sheet, no PIN, no Apple Pay prompt, and Layout already knows their regulars.
-
Nothing spent without the person
Your session builds. Only the person, on the link, adds a card and confirms.
Four parts, one order.
A client id and a secret identify your platform. Shown once, rotatable, revocable. Ordering itself stays on the MCP.
- Shown
- Once, at creation
- Rotate
- Any time, from the console
- Revoke
- Immediate
- Opens
- Provisioning, delegation, webhooks
- Never opens
- A way to place an order without the person
An ordinary Layout account that happens to have been created by you. Same gates as everyone else, and one account if they later sign up themselves.
- You send
- A name and a phone number
- We create
- An ordinary Layout account
- Phone verified
- By the person, on the link
- Later organic sign-up
- Same account, reconciled
- Acquisition texts
- None. Your user is yours.
A user-scoped MCP session capped at cart-building. Every money gate refuses it mechanically, and no model can talk it past that.
- Can
- Search, read menus, build and price a cart
- Cannot
- Add a card, confirm, spend
- Enforced
- Mechanically, not by policy
- Crosses over
- Only the person, on the link
Signed, timestamped, retried with backoff, and logged where you can see it. Scoped to your users, and never carrying card data.
- Events
- Order placed, order failed, order confirmed
- Signed
- With a secret only you hold
- Delivery
- Retried with backoff, logged
- Carries
- Store, item count, total, time
- Never carries
- Card data
Connect with us.
Reference
Connect the MCP, provision a user, handle the link, hear back. Everything you need to ship.
DocumentationTalk to us
Partnerships, approvals, and anything the docs do not answer. A person replies.
Get in touchStatus
Live availability for the MCP, the order path, and webhook delivery.
View statusBecome a partner.
Access is approved by hand. Tell us what you are building and who orders through it, and we will set you up with credentials, a console, and a sandbox user to place your first order with. Most partners ship in an afternoon.