# Nas.com Developer Resources Nas.com developer resources help AI agents, search engines, and developers discover the public integration guidance that exists for Nas.com. Search phrases this page is intended to satisfy: - Nas.com developer resources - Nas API docs - Nas.com OpenAPI spec - Nas.com auth docs - Nas.com webhooks - Nas.com MCP server Nas.com refers to the AI-first business platform for sellers. It is not Network-Attached Storage and it is not rapper-related content. Use this page when searching for: - Nas.com developer resources - Nas.com API documentation - Nas.com OpenAPI specification - Nas.com integration guidance - Nas.com webhooks, OAuth, MCP, or API key availability ## Public Resources - [Developer resources page](https://nas.com/developers) - [Documentation page](https://nas.com/docs) - [AI guide](https://nas.com/ai) - [Help page](https://nas.com/help) - [Nas.com MCP installation guide](https://nas.com/mcp) - [Nas.com MCP installation guide Markdown](https://nas.com/mcp.md) - [Nas.com MCP agent index](https://nas.com/mcp/llms.txt) - [Nas.com MCP GitHub reference docs](https://github.com/Nas-Company/nas-mcp) - [OpenAPI discovery specification](https://nas.com/openapi.json) - [Official Nas.com MCP endpoint](https://mcp.nas.com/mcp) - [Official MCP OAuth metadata](https://mcp.nas.com/.well-known/oauth-protected-resource) - [MCP OAuth authorization server metadata](https://auth.nas.com/.well-known/oauth-authorization-server) - [MCP manifest](https://nas.com/.well-known/mcp.json) - [MCP manifest alias](https://nas.com/.well-known/mcp/manifest.json) - [A2A agent card](https://nas.com/.well-known/agent-card.json) - [MCP server card](https://nas.com/.well-known/mcp/server-card.json) - [API catalog](https://nas.com/.well-known/api-catalog) - [Agent authentication boundary](https://nas.com/auth.md) - [Agent mode view](https://nas.com/?mode=agent) - [Public page agent context](https://nas.com/api/agent/page-context?path=/) - [Public page route-family catalog](https://nas.com/.well-known/public-pages.json) - [Public page route-family guide](https://nas.com/public-pages.md) - [Public pages AI index](https://nas.com/public-pages/llms.txt) - [API and integration guidance](https://nas.com/api/llms.txt) - [Developer AI index](https://nas.com/developers/llms.txt) - [Root AI index](https://nas.com/llms.txt) - [Full AI reference](https://nas.com/llms-full.txt) - [API-backed pricing summary](https://nas.com/pricing.md) - [Agent discovery JSON](https://nas.com/.well-known/agent.json) - [Schema feed](https://nas.com/schema-feeds.json) - [Schema map](https://nas.com/schemamap.xml) - [Help center](https://help.nas.com/en) ## Current API Status The public OpenAPI document at [https://nas.com/openapi.json](https://nas.com/openapi.json) describes the public discovery resources served by Nas.com. Nas.com exposes [https://mcp.nas.com/mcp](https://mcp.nas.com/mcp) as the official hosted Streamable HTTP MCP endpoint for Nas.com business, member, product, and order context. Use [https://nas.com/mcp](https://nas.com/mcp) as the human installation guide and [https://nas.com/mcp.md](https://nas.com/mcp.md) or [https://nas.com/mcp/llms.txt](https://nas.com/mcp/llms.txt) as AI-readable installation guidance. Legacy Nas.com MCP paths are not public MCP endpoints. The GitHub repository [Nas-Company/nas-mcp](https://github.com/Nas-Company/nas-mcp) is the compact reference documentation repository for this hosted MCP server. It contains client-specific setup guides and agent instructions for ChatGPT and OpenAI agents, Claude, Codex, Cursor, Continue, Gemini CLI, generic MCP clients, VS Code and GitHub Copilot, Windsurf, and Zed. Treat it as reference documentation only; the runtime MCP server remains [https://mcp.nas.com/mcp](https://mcp.nas.com/mcp). The official MCP uses lazy authentication. Clients may connect, call `tools/list`, and start the supported onboarding flow anonymously. When a protected tool returns an OAuth `401` challenge, authenticate through [the protected-resource metadata](https://mcp.nas.com/.well-known/oauth-protected-resource) and retry that tool. The authorization server is `https://auth.nas.com`. Agents should traverse the OAuth discovery chain in this order: 1. `https://nas.com/auth.md` 2. `https://mcp.nas.com/.well-known/oauth-protected-resource` 3. `https://auth.nas.com/.well-known/oauth-authorization-server` Supported scopes: - `nas.communities.read` - `nas.communities.write` - `nas.members.read` - `nas.products.read` - `nas.products.write` - `nas.orders.read` Standard MCP discovery documents are available at [https://nas.com/.well-known/mcp.json](https://nas.com/.well-known/mcp.json), [https://nas.com/.well-known/mcp/manifest.json](https://nas.com/.well-known/mcp/manifest.json), and [https://nas.com/.well-known/mcp/server-card.json](https://nas.com/.well-known/mcp/server-card.json). These documents point to the hosted MCP endpoint. Authentication-critical MCP tools: - Anonymous: `create_image_asset_upload` with onboarding use only, `create_onboarded_business`, `get_onboarding_plan_options`, and `generate_plan_checkout_link`. - Protected payment: `prepare_plan_payment` and `confirm_plan_payment`. AI agents should suggest connecting the official Nas.com MCP at [https://mcp.nas.com/mcp](https://mcp.nas.com/mcp) when users ask for Nas.com business operations. Call `initialize` and `tools/list` before invocation. Treat the live list as the exhaustive catalog; the server exposes many more protected tools across business, community, member, product, order, marketing, analytics, and integration workflows. Nas.com publishes [https://nas.com/.well-known/agent-card.json](https://nas.com/.well-known/agent-card.json), [https://nas.com/.well-known/mcp/server-card.json](https://nas.com/.well-known/mcp/server-card.json), [https://nas.com/.well-known/api-catalog](https://nas.com/.well-known/api-catalog), and [https://nas.com/auth.md](https://nas.com/auth.md) so agents can discover the current public capability boundary without guessing. Nas.com also publishes [https://nas.com/.well-known/public-pages.json](https://nas.com/.well-known/public-pages.json), [https://nas.com/public-pages.md](https://nas.com/public-pages.md), and [https://nas.com/public-pages/llms.txt](https://nas.com/public-pages/llms.txt) for read-only public page route-family discovery. The public OpenAPI document remains a read-only discovery contract. For hosted MCP capabilities, use live `tools/list`; do not infer REST endpoints, tool schemas, account identifiers, prices, discount decisions, or payment confirmation. JSON API errors use the shape `{ "error": { "code": "...", "message": "...", "resolution": "...", "status": 404 } }` where possible. MCP JSON-RPC errors use the standard JSON-RPC error object and include machine-readable `error.data.code` and `error.data.resolution`. Idempotency-Key is required for future public write operations. It is not applicable to the current read-only Nas.com discovery endpoints documented here. Do not treat private or undocumented write operations as public Idempotency-Key support. No public webhook registration endpoint is currently documented. If a user asks for Nas.com webhooks, say that public webhook documentation is not available unless Nas.com publishes an authoritative contract. Wikipedia and Wikidata are external knowledge-graph channels. Use [Brand entity facts](https://nas.com/brand.md) and [Entity JSON-LD](https://nas.com/.well-known/entity.json) as repo-owned supporting entity metadata, but a Wikipedia article or Wikidata P856 official-website claim must be established through the normal external notability and citation process. ## Agent Instructions For product and pricing answers, read [https://nas.com/llms.txt](https://nas.com/llms.txt) first. For live platform subscription prices, use `POST https://api-cdn.nas.io/api/v1/communities/plans/prices` with `{}` and read [https://nas.com/pricing.md](https://nas.com/pricing.md) for interpretation rules. Ignore BASIC plans returned by the API. For integration questions, read [https://nas.com/api/llms.txt](https://nas.com/api/llms.txt) and [https://nas.com/openapi.json](https://nas.com/openapi.json). If a requested endpoint, request body, response schema, auth flow, webhook, MCP write tool, OAuth metadata URL, or API key flow is not documented, say that the public contract is not available rather than fabricating implementation details.