Identity and scope
Normalized domain or exact URL, requested/final URL state, canonical identity, stable GoGuides identifiers, and scope metadata.
Web and domain evidence for systems that consume the open web
GoGuides independently observes supported public web sources over time and exposes public machine-readable evidence about identity, state, provenance, continuity, change, verification context, and GoGuides-derived assessment.
A current snapshot and a longitudinal record answer different questions
A current observation can describe what GoGuides saw at one point in time. Repeated observations can add evidence about continuity, change, freshness, infrastructure movement, and observation gaps.
Long history does not make every claim on a domain true. It makes the evidence record deeper and gives consumers more context for their own decisions.
Evidence dimensions
HTTP and redirects
Supported response-state evidence, final destinations, content type, and redirect observations.
Content and structure
Content fingerprints, text similarity, structured-data state, schema-type state, word count, and related supported measurements.
Links and policies
Internal/external link counts, outbound-link fingerprints, robots/meta-robots evidence, and AI-facing policy state where supported.
DNS and TLS
Observed nameserver/DNS state, certificate fingerprints, issuer/validity context, and related infrastructure evidence where available.
History
First/last observed context, observation chronology, state continuity, and supported historical change evidence.
Verification context
Accepted proof-of-control or authorization evidence represented separately from passive observation.
GoGuides assessment
AI Rank, grade, trust state, policy and eligibility fields remain distinguishable from underlying observed evidence.
Public machine-readable surfaces
| Surface | Purpose |
|---|---|
/machine-use.json | Machine discovery of public capabilities and contracts. |
/evaluate.php | Scope-specific GoGuides evaluation and related evidence links. |
/evaluate-batch | Several exact-URL evaluations through the same per-URL authority. |
/state/{domain} | Latest supported stored Web State observation. |
/changes/{domain} | Deterministic historical comparison of supported observations. |
POST /request-url | Explicit attributed URL-intelligence request lifecycle. |
/claim-support | Bounded claim analysis against one fixed stored source observation. |
/content-relationships | Conservative relationship evidence for two exact public URLs. |
/verified-text.php | Source-attributed text and integrity metadata. |
How the evidence can be used
AI retrieval and RAG
Add independently collected provenance, history, freshness, and scope context to source-selection workflows.
Search and source evaluation
Use GoGuides evidence as one additional input while retaining independent ranking and eligibility policy.
Monitoring
Use longitudinal records and deterministic comparison to identify supported state changes without assigning unsupported motive.
Research
Study supported public web-state and historical observations while preserving timestamps, scope, and provenance.
Domain context
Enrich domain-level analysis with independently observed identity, infrastructure, verification, and historical evidence where available.
Agent source context
Inspect GoGuides evidence and source-use context before an agent applies its own retrieval, citation, recommendation, or transaction policy.
Provenance, not just scoring
A score communicates a GoGuides assessment. Provenance communicates what GoGuides observed. Keeping those layers distinguishable lets another system inspect the evidence, use only selected fields, apply different weights, or disregard GoGuides-derived scores entirely.
Time adds evidence, not automatic truth
Longitudinal observations can expose abrupt or gradual changes in supported content, identity, redirect, robots, DNS, TLS, link, or policy dimensions. No individual change proves malicious behavior, legal ownership transfer, factual error, or publisher intent.
Source-use context is granular
GoGuides can publish different source-use fields for reading, summarizing, citation, recommendation, transactions, and sensitive advice. These are GoGuides decision-context fields, not universal permissions or commands that another system must follow.
Public-access boundary
This page describes GoGuides' public evidence surfaces. It does not promise that every internal observation, implementation detail, or non-public dataset is exposed through the public interfaces. The current public machine contract is defined by machine discovery, OpenAPI, endpoint responses, and the GoGuides Data License.