robots.txt
See which AI crawlers other sites block →# https://www.robotstxt.org/robotstxt.html
#
# Content-Signal declares the permitted *use* of what a crawler fetches, independently of whether
# it may fetch at all: this site may be indexed for search and used as input to an AI answer
# (grounding/RAG), but its content is not offered for model training.
# https://contentsignals.org
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
# Sign-in endpoints 302 to the identity provider with a new session id on every request.
# Crawling them spends budget on URLs that are never pages. Other /api paths (the published
# JSON and llms.txt documents below) stay allowed.
Disallow: /api/auth/
Sitemap: https://layer.ai/sitemap-index.xml
# /docs is a separate Astro build behind the same origin, so it emits its own sitemap. Both
# are listed here: robots.txt is the only place a crawler is told a sitemap exists, and the
# root index covers the marketing build alone.
Sitemap: https://layer.ai/docs/sitemap-index.xml
# ── AI crawlers ──
#
# robots.txt groups do not merge: a crawler that matches a named group ignores the `*` group
# entirely. Every group below therefore repeats Content-Signal, or these agents would see no
# signal at all.
# Crawlers behind an answer engine, and the user-triggered fetchers that back "open this page"
# in an assistant. Allowed: being absent from ChatGPT, Claude, and Perplexity costs Layer more
# than any crawl budget. Training remains unpermitted — that is what Content-Signal says, and it
# applies to these agents too.
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Applebot-Extended
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /
# Repeated from the `*` group: a named group does not inherit it.
Disallow: /api/auth/
# Crawlers that build training corpora and surface Layer in no answer engine, so there is nothing
# to lose by declining them. Disallowed as well as signaled, because a signal is a request and a
# disallow is an instruction.
User-agent: CCBot
User-agent: Bytespider
Content-Signal: search=yes, ai-input=yes, ai-train=no
Disallow: /
# LLM-readable content indexes (https://llmstxt.org)
# https://layer.ai/llms.txt
# https://layer.ai/llms-full.txt
# https://layer.ai/docs/llms.txt
# Agent mode for the home page — the same facts as / in a dense, machine-first form
# https://layer.ai/?mode=agent (also /agent, /agent.md)
# Machine-readable API surface
# https://layer.ai/.well-known/api-catalog (RFC 9727 API catalog)
# https://layer.ai/.well-known/mcp (Layer MCP servers + tool lists)
# https://layer.ai/.well-known/ard.json (ARD manifest: every callable Layer resource)
# https://layer.ai/.well-known/ai-catalog.json (APIs + readable content surface, for AI clients)
# https://layer.ai/.well-known/agent-skills/index.json (Agent Skills index: one SKILL.md per capability)
# https://layer.ai/openapi.json (Layer REST API, OpenAPI 3.1)
# https://layer.ai/api/index.json (REST + MCP entry points, auth, limits, policy)
# https://layer.ai/api/onboarding.json (self-serve signup, credentials, zero-auth URLs)
# OAuth 2.0 discovery — these paths redirect to the authoritative host, which is where RFC 8414
# and RFC 9728 require the metadata to be served from.
# https://layer.ai/.well-known/oauth-authorization-server -> https://auth.app.layer.ai/...
# https://layer.ai/.well-known/oauth-protected-resource -> https://mcp.app.layer.ai/...
# Developer documentation
# https://layer.ai/docs (Layer developer documentation)
# https://layer.ai/docs/authentication (Layer API authentication)
# https://layer.ai/docs/rate-limits (Layer API rate limits)
# https://layer.ai/docs/versioning (Layer API versioning)
# https://layer.ai/docs/deprecation (Layer API deprecation policy)
# Markdown variants: append .md to any page path, or send `Accept: text/markdown`
# (https://acceptmarkdown.com)
llms.txt
Compare with other sites' llms.txt files →# Layer
> Layer is the AI platform for creative teams in the entertainment industry. Generate and edit images, video, 3D models, and audio assets with leading AI models in one workspace. Built for game studios with enterprise security, workflow automation, and team collaboration.
Layer provides 500+ AI models across four modalities (image, video, 3D, audio), custom style training, node-based workflow automation, and enterprise features like SOC 2 Type II compliance, SSO/SCIM, and role-based access controls. Used by 400+ game studios worldwide.
## Core Pages
- [Home](https://layer.ai/): AI platform overview for creative teams
- [Features](https://layer.ai/features): Platform capabilities and creative automation features
- [Pricing](https://layer.ai/pricing): Usage-based pricing with Creative Units, no seat fees
- [Pricing (machine-readable)](https://layer.ai/pricing.md): Full pricing table in Markdown format
- [Pricing Calculator](https://layer.ai/pricing/calculator): Configure models and estimate costs
- [Enterprise](https://layer.ai/enterprise): Enterprise features, security, and compliance
- [Models](https://layer.ai/models): The catalog, 407 models across image, video, 3D, and audio
- [Tools](https://layer.ai/tools): Workflow templates for creative production
- [MCP Server](https://layer.ai/mcp) ([md](https://layer.ai/mcp.md)): Connect Claude, Cursor, VS Code, Codex, and any MCP client to Layer
- [Agent Skills](https://layer.ai/agent-skills) ([md](https://layer.ai/agent-skills.md)): Thirty-two skills teaching a coding agent creative craft on Layer, installed with `npx skills add layerai/skills --skill "*"`
- [Command-Line Interface](https://layer.ai/cli) ([md](https://layer.ai/cli.md)): The `layer` CLI — generate from a terminal or a CI job, with JSON output and documented exit codes
- [Use Cases](https://layer.ai/use-cases): Use cases for characters, UI, environments, and marketing assets
- [Blog](https://layer.ai/blog): Guides, updates, and news
- [Success Stories](https://layer.ai/success-stories): Case studies from game studios
- [Glossary](https://layer.ai/glossary) ([md](https://layer.ai/glossary.md)): The vocabulary of AI asset production
- [Contact Sales](https://layer.ai/contact-sales): Talk to the Layer sales team
## Section Indexes
- [Models llms.txt](https://layer.ai/models/llms.txt): Every model in the catalog, by modality, with its provider and what it is for.
- [Tools llms.txt](https://layer.ai/tools/llms.txt): Every workflow template, with what it produces.
- [Features llms.txt](https://layer.ai/features/llms.txt): Platform capabilities, use cases, industries, integrations, and the pages written for each role.
- [API llms.txt](https://layer.ai/api/llms.txt): The developer surface in one document: REST, MCP servers and their tools, OAuth, and what it takes to connect an agent.
- [Blog llms.txt](https://layer.ai/blog/llms.txt): Every post and every customer success story.
- [Glossary llms.txt](https://layer.ai/glossary/llms.txt): Every glossary term, defined.
- [Docs llms.txt](https://layer.ai/docs/llms.txt): LLM-readable index of the developer documentation
## Resources
- [Partners](https://layer.ai/partners): Model providers and technology partners
- [About](https://layer.ai/about): Team, mission, and company information
- [Careers](https://layer.ai/careers): Open positions at Layer
- [Changelog](https://layer.ai/changelog): What shipped, release by release
## Connecting an Agent
- Layer MCP Server: `https://mcp.app.layer.ai/mcp` (streamable-http, OAuth 2.0) — Generate and edit images, video, 3D, and audio; run Blueprint workflows; train styles; assemble video timelines; upload and score files.
- Layer Management MCP Server: `https://mcp.app.layer.ai/mcp-management` (streamable-http, OAuth 2.0) — Administer a workspace: projects, groups, members, roles, usage limits, and Creative Unit consumption. Kept separate so admin tools do not crowd the creative toolset.
- Authentication: OAuth 2.0 authorization code + PKCE against https://auth.app.layer.ai/, with dynamic client registration — no pre-registered client id and no API key. Metadata: https://auth.app.layer.ai/.well-known/oauth-authorization-server
- REST alternative: a Personal Access Token (`layer_pat_`) created self-serve in the app, carrying its creator's workspace permissions; or a workspace service account, whose key exchanges at /api/oauth/token for a token narrowed to API scopes.
- Getting started: sign up at https://layer.ai/login — self-serve, no sales contact required.
- [API llms.txt](https://layer.ai/api/llms.txt): The full developer surface, including what Layer does not offer
## For Agents
- [Agent mode for the home page](https://layer.ai/?mode=agent): Everything on this list's home page, plus the REST and MCP entry points, in one dense document (also https://layer.ai/agent.md)
- Every page listed above is also published as Markdown: append `.md` to the path, or request the page with `Accept: text/markdown` (see https://acceptmarkdown.com).
- [Sitemap](https://layer.ai/sitemap-index.xml): Every canonical URL on this site
- [llms-full.txt](https://layer.ai/llms-full.txt): Full-text index of the site
- [Pricing (JSON)](https://layer.ai/pricing.json): Machine-readable pricing data
- [OpenAPI](https://layer.ai/openapi.json): The REST surface, as an OpenAPI description
- [MCP Manifest](https://layer.ai/.well-known/mcp): Both Layer MCP servers, their transport, OAuth metadata, full tool lists, and the MCP Apps `ui://` views they render results with
- Missing paths return a real HTTP 404 with a Markdown recovery body ([/404.md](https://layer.ai/404.md)) or an RFC 9457 problem document ([/404.json](https://layer.ai/404.json)).
## Legal
- [Acceptable Use Policy](https://layer.ai/acceptable-use-policy)
- [Copyright Infringement Policy](https://layer.ai/copyright-infringement-policy)
- [Creator Network Program Terms](https://layer.ai/creator-network-terms)
- [Privacy Policy](https://layer.ai/privacy-policy)
- [Referral Program Terms](https://layer.ai/referral-program-terms)
- [Terms of Service](https://layer.ai/terms-of-service)