# 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.

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

- [OpenAPI discovery specification](https://nas.com/openapi.json)
- [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)
- [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.

It does not document a seller, creator, admin, payment, checkout, webhook, OAuth, MCP, or private integration API. Do not infer those contracts unless Nas.com publishes them or the user provides an authoritative API contract.

## Agent Instructions

For product and pricing answers, read [https://nas.com/llms.txt](https://nas.com/llms.txt) first.

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 endpoint, OAuth metadata URL, or API key flow is not documented, say that the public contract is not available rather than fabricating implementation details.