The verified data resolver for AI.
Enter a domain. Get the official machine resources published by its owner.
A DNS-like lookup model — one domain in, its authoritative pointers out.
For organizations
Show AI systems where your official resources live — a data file, an API, an agent endpoint, documentation. Everything stays on your own site; NessGate stores only verified pointers. To update a listing, register the same domain again with the full new list.
Prove you control — choose ONE option:
A. Create this file:
containing exactly:
B. Or add a DNS TXT record:
Name:
Value:
C. Or add this field to your JSON file:
The code expires in 60 minutes and works once. You can remove the file/record/field after verification. DNS changes can take a few minutes to become visible.
Remove a listing
For developers
One stable endpoint. No keys, no auth, open CORS.
GET https://nessgate.com/resolve/{domain}
curl https://nessgate.com/resolve/example.com
# → { "domain": "example.com", "verified": true,
# "resources": [ { "name": "Company data", "type": "json",
# "url": "https://example.com/ai-info.json" } ] }const res = await fetch("https://nessgate.com/resolve/example.com");
const { verified, resources } = await res.json();import requests
data = requests.get("https://nessgate.com/resolve/example.com").json()
# {"domain": ..., "verified": ..., "resources": [...]}API reference · Specification · OpenAPI · Registry · llms.txt
Your format
No required schema, no required protocol. JSON, APIs, MCP servers, agents, docs — declare any resource, even one NessGate has never heard of. AI systems read it directly from your URLs.
Your server
Your resources live on your own infrastructure, always. Like DNS, NessGate is just the router: it holds only the verified pointers.
Zero access
No passwords, no API keys, no server access, no code to install. Verification is a single read-only lookup of a public file or DNS record.