DNS
Published
Domain and edge records identify the HTTPS site and the native 9192/1 TLS endpoint.
Discovery graph
Every public signal points toward a verifiable 9192 execution path.
The node is discoverable through DNS, HTTPS metadata, agent descriptors, API status routes and the native TLS edge. This page is the human-readable map of that surface.
Well-known
Machine-readable
/.well-known/9192/ exposes bootstrap, status, pricebook, manifest and service catalog documents.
Agents
Crawler-ready
/agents.json, /agent-directory.json, /mcp.json and /llms.txt help agents understand the available public interface.
Path to execution
DNS -> site -> .well-known -> agents -> API or native edge -> quote -> execution -> receipt verification
Native edge
9192/1
edge.nineoneninetwo.com.br:9443 is the binary protocol edge for direct machine clients.
HTTPS API
Facade
/api/v1/status, /api/v1/health and sandbox routes give external clients a simpler first integration path.
Verification
Receipts
Clients can verify results and receipts instead of trusting a page claim or marketing statement.
Operational reports
Local reports track operational trust, traffic and DNS reputation. Public snapshots expose only discovery-safe metadata and avoid raw client IPs.
run_9192_discovery_map_windows.ps1 -PublishPublicSnapshot