A guide for coding agents
Coding agents is a new guide for handing a Layout integration to a coding agent. It names the one step a person does first (sign up and make a CLI token), what the agent runs from there, the rules it must follow, and a prompt to start it with. llms.txt now points an agent to it first.
What changed
- One name for your secret. Every reference example now reads the secret from
LAYOUT_SECRET_KEY, the variable the CLI already reads, instead ofLAYOUT_SECRET. The quickstart no longer asks for the client id, which no step uses. - Going to production. Going to production said swapping in the
sk_live_secret was the whole migration. It now also covers the production signing secret, what answers differently in production (phone numbers, test restaurants, confirms), and keepingsk_live_and development webhook endpoints away from production. - Calling person routes from the CLI. The Call the API example sent
GET /v1/placeswith your key, which answers401. Places, menus, item images and carts take a person's build grant or access token in--token. - The listen secret.
layout listensigns with a new secret on every run. The CLI reference now says to give your server that run's secret each time. - Sandbox confirms. A sign-in test account's confirm over REST answers
placing, as every REST confirm does. The page saidplaced. - The retired order route.
POST /v1/ordersis markeddeprecatedin openapi.json, so a client generated from it flagscreateOrder, which always answers410. Build withPOST /v1/carts. - Markdown copies. The Markdown version of every page, and
llms-full.txt, now show characters such as•and×instead of their HTML codes.
What to do
Nothing. If you generated a client from openapi.json and it calls createOrder, move that call to Carts; it has answered 410 since the route was retired.
Breaking changes
None. The API did not change; the pages now describe what it already does.