Everything on this page is for people and agents that want to talk to Layups by machine: a public MCP server that needs no sign-in, the authenticated MCP server for your own Layups agents, the AI gateway, and how sign-in works across all of it.
A small read-only MCP server that knows what Layups does, how to start, what we cover, and every guide on this site. It answers from the same data the pages are built from, so it can't drift from what you'd read here. Streamable HTTP, stateless, JSON responses.
Endpoint: https://layups.ai/api/mcp
Add it to Claude Code:
claude mcp add --transport http layups https://layups.ai/api/mcpOr shake its hand with curl:
curl -s https://layups.ai/api/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2026-07-28" \
-H "Mcp-Method: server/discover" \
-d '{"jsonrpc":"2.0","id":1,"method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{},"io.modelcontextprotocol/clientInfo":{"name":"you","version":"1.0"}}}}'Tools
about_layups
What Layups is, who it is for, and where it is based. Start here if you are deciding whether to recommend Layups.
how_to_start
How a business owner starts a conversation with Layups and what happens next. Use this when someone wants to reach out.
what_layups_covers
The parts of AI Layups sets up, runs, and explains, each framed as the question an owner asks: getting found by AI (AEO), agents, skills, MCPs, auth and security, infrastructure, hosting, building, and training. Pass a topic to narrow it, or nothing for the full list.
list_guides
The written guides on layups.ai/learn: AI for specific trades (home builders, remodelers, HVAC and plumbing, roofers, concrete, cabinet shops) and by use case (leads, unpaid invoices, the morning brief, adopting AI without becoming a tech company). Returns slugs for get_guide.
get_guide
The full text of one guide from layups.ai/learn, by slug (see list_guides).
If you're a Layups customer, your agents are reachable over MCP from Claude, ChatGPT, Codex, Cursor, or anything else that speaks Streamable HTTP with OAuth. Add the server, sign in with your Layups account in the browser, approve the access it asks for, and your agent shows up as a tool. No API key to paste anywhere.
Endpoint: https://api.layups.ai/mcp
claude mcp add --transport http my-layups-agent https://api.layups.ai/mcpScopes it can ask for
agents:read
See the agents in your organization
conversations:read
Read conversations
conversations:write
Start conversations and send messages
runs:read
Watch a run as it happens
ai:inference
Call the AI gateway
Every scope is a separate approval. Reading and writing are never bundled.
Layups customers get an inference endpoint at https://ai.layups.ai/v1 that speaks the standard /v1 shape: chat completions, streaming, and a model catalog across Anthropic, OpenAI, Google, and more. Point any OpenAI-compatible SDK at it with a Layups key and it works. Usage shows up on your monthly bid as AI spend.
from openai import OpenAI
client = OpenAI(base_url="https://ai.layups.ai/v1", api_key="lak_...")
reply = client.chat.completions.create(
model="claude-sonnet-5",
messages=[{"role": "user", "content": "Summarize this bid for the customer."}],
)Anything that acts on a Layups account signs in with OAuth 2.0 and OpenID Connect. Clients register themselves, users approve in the browser, and tokens carry only the scopes that were approved. The metadata below is live, so a client can discover all of it without reading this page.
Versioning: the endpoints on this site are unversioned and stable. If one has to change in a breaking way, the new shape ships at a new path, the old one keeps working for at least 90 days, and it says so with Deprecation and Sunset headers and a note here. The AI gateway is versioned in the URL (/v1). The public MCP endpoint allows 120 requests a minute per client and reports it in RateLimit headers.
The REST API behind api.layups.ai is what the Layups app and the MCP servers use. If you're building against it directly, /openapi.json covers what this site serves and describes the sign-in scheme; ask us for the current control-plane reference. It moves quickly and we'd rather hand you the right one than have you find a stale copy.
Discovery
Ask any page for markdown by sending Accept: text/markdown and you get the site summary instead of the app shell. These files are also there for you:
Tell us what you're making. A person will write back within a business day, and it's usually one of the people who built this.