Independent observation
GoGuides records what it observed from public web sources rather than simply republishing a publisher's self-description as independent fact.
Public web intelligence built from independent observations over time
GoGuides exposes public machine-readable surfaces for provenance, current stored state, evaluation, deterministic change evidence, verification context, bounded analysis and machine capability discovery.
What the public data surfaces represent
Longitudinal state
Repeated observations can support history, freshness analysis, deterministic comparison and evidence about change over time.
Provenance
Source identity, scope, timestamps, hashes and observation metadata help a consumer determine where a record came from and what it actually represents.
Derived assessment
AI Rank, grade, trust state and related GoGuides assessments stay distinguishable from objective observation fields.
Deterministic comparison
Change Intelligence reports supported differences between concrete stored observations without inventing semantic certainty.
Bounded analysis
Claim Support and Content Relationships add constrained analysis layers while preserving the underlying evidence and limits.
Public access points
| Surface | Purpose |
|---|---|
| Evaluate | Root/domain and exact-URL evaluation. |
| Batch Evaluate | Multiple evaluations in one request. |
| Web State V3 | Latest supported stored observation state. |
| Change Intelligence | Deterministic historical comparison. |
| URL Request | Explicit attributed request for intelligence on a public URL. |
| Claim Support | Bounded model-assisted analysis of one stored source observation. |
| Content Relationships | Stored-evidence relationship comparison for two exact URLs. |
| Verified Text | Source-attributed text records with integrity metadata. |
| machine-use.json | Machine-readable capability discovery. |
| OpenAPI 3.1 | Formal public API contract. |
Examples of evidence dimensions GoGuides can preserve
Availability varies by scope and observation. Supported records can include state such as content fingerprints, text similarity signatures, structured-data hashes and type masks, response-header fingerprints, word counts, internal and external link counts, outbound-link fingerprints, AI-policy observations, HTTP and redirect state, timestamps and provenance metadata.
A missing field should remain missing or unavailable. The purpose is to expose what GoGuides
actually observed, not to fill gaps with guesses.
How consumers can use the data
Source intake
Add independent web evidence to a retrieval, citation, research or source-evaluation workflow.
Change monitoring
Identify supported state changes before deciding whether deeper recrawling or analysis is warranted.
Provenance checks
Track the source, scope and observation lineage behind a machine-readable record.
Quality control
Compare evidence classes without treating a derived score as a substitute for underlying observations.
Research datasets
Use public records under the applicable GoGuides data-license terms and documented endpoint contracts.
Source-use decisions
Apply your own ranking, safety, citation, eligibility and recommendation policy to the evidence GoGuides exposes.
Access and licensing
Public GoGuides interfaces are documented through the Developer Hub, machine-use discovery, focused human documentation and OpenAPI. The applicable terms for use and redistribution are described in the GoGuides Data License.
This page describes public data surfaces; it is not a promise that every internal observation, operational field or bulk dataset is exposed through every public endpoint.