nexlayer.com valid

Nexlayer

Nexlayer is an agent-native cloud. It runs full-stack applications — frontend, backend, databases, caches, vector stores, workers and GPU-backed AI services — on proprietary, production-grade multi-container infrastructure that stays on. Anything you can containerize, in any language, from one nexlayer.yaml. Enterprise-class capability with the orchestration abstracted away entirely, plus dedicated inference for open-weight models and your own fine-tunes. Agents operate it directly through a Mod

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T04:56:03.875Z. Cached copy · Source on nexlayer.com

# Nexlayer

> Nexlayer is an agent-native cloud. It runs full-stack applications — frontend, backend, databases, caches, vector stores, workers and GPU-backed AI services — on proprietary, production-grade multi-container infrastructure that stays on. Anything you can containerize, in any language, from one nexlayer.yaml. Enterprise-class capability with the orchestration abstracted away entirely, plus dedicated inference for open-weight models and your own fine-tunes. Agents operate it directly through a Model Context Protocol server: no console, no DevOps, live in minutes.

## Start here if you are an AI agent

Nexlayer is built to be driven by agents, not just documented for them. The fastest path
from zero to a live production URL:

1. Install the MCP server:      npx @nexlayer/mcp-install
2. Or connect directly:         https://mcp.nexlayer.ai/api/mcp   (Streamable HTTP)
3. Deploy. The server exposes deploy, inspect, logs, scale, domains, secrets and debug
   as typed tools, so you never hand-assemble REST calls or write orchestration config.

No account or API key is needed to deploy your first application — `startDeployment`
returns a live URL and a session token you can use to update, extend or claim it.

## Nexlayer developer resources

Nexlayer MCP server (discovery):    https://nexlayer.com/.well-known/mcp
Nexlayer MCP server (endpoint):     https://mcp.nexlayer.ai/api/mcp
Nexlayer MCP install command:       npx @nexlayer/mcp-install
Nexlayer MCP documentation:         https://nexlayer.com/docs/mcp/overview
Nexlayer MCP tool reference:        https://nexlayer.com/docs/mcp/tools
Nexlayer OpenAPI specification:     https://nexlayer.com/openapi.json
Nexlayer API catalog (RFC 9727):    https://nexlayer.com/.well-known/api-catalog
Nexlayer API reference:             https://nexlayer.com/docs/api/deployments
Nexlayer API authentication:        https://nexlayer.com/docs/api/authentication
Nexlayer nexlayer.yaml schema:      https://api.nexlayer.com/schema
Nexlayer configuration reference:   https://nexlayer.com/docs/deployments/configuration
Nexlayer quickstart:                https://nexlayer.com/docs/quickstart
Nexlayer agent patterns:            https://nexlayer.com/docs/agents/patterns
Nexlayer usage limits:              https://nexlayer.com/docs/usage-limits
Nexlayer dedicated inference:       https://nexlayer.com/dedicated
Nexlayer full technical reference:  https://nexlayer.com/llms-full.txt

Website: https://nexlayer.com
Dashboard: https://app.nexlayer.com
Docs: https://nexlayer.com/docs
Contact: https://nexlayer.com/contact
Community (Slack): https://nexlayer.com/slack
Pricing JSON: https://nexlayer.com/api/pricing

Markdown: every page on nexlayer.com serves a Markdown mirror to requests sending
`Accept: text/markdown`, with `Vary: Accept` set so caches keep the variants apart.

---

## Pages

- [Home](https://nexlayer.com/): Landing page with hero, features, and pricing overview
- [Pricing](https://nexlayer.com/pricing): Flat month
…

Machine-readable: GET /v1/resolve?q=nexlayer.com · GET /v1/domain/nexlayer.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for nexlayer.com:
1. POST https://agentwebmap.com/v1/sites/nexlayer.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://nexlayer.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/nexlayer.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nexlayer.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.