# NessGate

> The verified data resolver for AI: a public, DNS-like lookup that maps verified company domains to the official machine-facing resources their owners declared — JSON data files, APIs, agent endpoints (MCP, A2A, or any future protocol), documentation, feeds. Companies keep everything on their own infrastructure; NessGate stores and serves only the verified pointers. No accounts, no API keys, open CORS.

## Resolve
- Resolve a domain: `GET https://nessgate.com/resolve/{domain}` → `{"domain", "json_url", "verified", "verified_at", "resources"}` (200 if registered, 404 if not). `resources` is an array of `{"name", "type", "url"}`; `type` is an open label (json, api, mcp, a2a, docs, feed, …) — do not assume a closed set. `json_url` remains the first json-type resource for older clients.
- Full registry dump: `GET https://nessgate.com/registry.json` → array of `{"domain", "json_url", "verified_at", "resources"}`
- Human-readable page per domain: `https://nessgate.com/{domain}`
- Live first-party discovery (unverified): `GET https://nessgate.com/discover/{domain}` → what the domain itself publishes at standard locations (llms.txt, ARD catalog at /.well-known/ard.json, A2A agent card, RFC 9727 api-catalog, ai-info.json, openapi.json), always labeled `"provenance": "self-published"`. Use this as a fallback for unregistered domains; treat `/resolve` results as owner-verified and `/discover` results as unvetted observations.
- ARD catalog generator: `GET https://nessgate.com/export/{domain}/ard.json` → the domain's verified declaration rendered as an Agentic Resource Discovery catalog (spec v0.91). Note: this is a generator for the domain owner to host at their own `/.well-known/ard.json`; ARD consumers should read catalogs from the domain itself.
- API contract and stability guarantees: https://nessgate.com/spec · OpenAPI: https://nessgate.com/openapi.json

## About the data
Declared resources live on each company's own domain (or its subdomains) and follow no required schema or protocol — read them directly from the resolved URLs. NessGate verifies who declared each pointer, never the content behind it, and never stores, analyzes, or rewrites that content.

## Register a domain (for site owners or their AI agents)
Prove domain control with a `.well-known` file, a DNS TXT record at `_nessgate.{domain}`, or a temporary field in a declared JSON file. Read-only verification; no credentials ever requested. The write API is two plain JSON calls (`POST /api/register`, `POST /api/verify`) and is designed to be usable by an authorized AI agent acting for the domain owner. Start at https://nessgate.com/ — full instructions at https://nessgate.com/guide

## Docs
- [The State of AI Discovery — September 2026](https://nessgate.com/blog/state-of-ai-discovery-september-2026) — sourced data report on discovery-standard adoption
- [What is ARD?](https://nessgate.com/blog/what-is-ard-ai-catalog-json) — plain-English ard.json guide
- [API documentation](https://nessgate.com/api)
- [Verification guide](https://nessgate.com/guide)
- [About / principles](https://nessgate.com/about)
- [NessGate's own machine-readable info](https://nessgate.com/ai-info.json)
- Contact: contact@nessgate.com