Integrate with GoGuides web-evidence infrastructure

Evidence classes

Public capability map

Workflow 1: Discover the service

curl -sS 'https://www.goguides.com/machine-use.json'

Use machine discovery to locate supported interfaces and canonical documentation. Use OpenAPI when methods, parameters, schemas, limits, or error behavior matter to an implementation.

Workflow 2: Evaluate a domain or exact URL

curl -sS \
  'https://www.goguides.com/evaluate.php?domain=goguides.com&format=json'

curl -sS \
  'https://www.goguides.com/evaluate.php?url=https%3A%2F%2Fwww.goguides.com%2Fdata-license&format=json'

Root/domain and exact-page records are different scopes. The same normalized scope should resolve through the same authoritative GoGuides evaluation path wherever it appears.

Workflow 3: Batch Evaluate exact URLs

curl -sS --get \
  --data-urlencode 'url=https://www.goguides.com/data-license' \
  --data-urlencode 'url=https://www.iana.org/help/example-domains' \
  'https://www.goguides.com/evaluate-batch'

curl -sS \
  -H 'Content-Type: application/json' \
  --data '{"urls":["https://www.goguides.com/data-license","https://www.iana.org/help/example-domains"]}' \
  'https://www.goguides.com/evaluate-batch'

Batch Evaluate preserves per-item normalized scope and input order. It does not create a separate ranking or policy authority. Current public request limits belong to the formal machine contract and should be read from machine discovery and OpenAPI.

Workflow 4: Explicitly request intelligence for one URL

curl -sS \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{"url":"https://example.com/article","freshness":"use-current-or-crawl-on-miss"}' \
  'https://www.goguides.com/request-url'

A usable known result can be returned immediately. An accepted asynchronous request can return HTTP 202, a public request ID, status URL, and retry guidance. The caller records request intent; it does not write the resulting GoGuides evidence or assessment.

GET /request-url/status/gur_...

Treat the status resource as the public request lifecycle. Private processing details are not part of the public contract.

Read the focused URL Request documentation.

Workflow 5: Inspect Web State and Change Intelligence

curl -sS 'https://www.goguides.com/state/goguides.com'

curl -sS 'https://www.goguides.com/changes/goguides.com?limit=10'

Web State exposes the latest supported stored observation. Change Intelligence compares supported observation pairs deterministically. Missing history, observation gaps, and unknown states should remain uncertainty rather than being converted into invented conclusions.

Workflow 6: Claim Support and lifecycle status

curl -sS \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{"url":"https://www.goguides.com/data-license","claim":"GoGuides publishes a data license."}' \
  'https://www.goguides.com/claim-support'

Claim Support analyzes one claim against one fixed stored GoGuides source observation. Verdicts can include supported, contradicted, unaddressed, insufficient_evidence, and source_unavailable. The analysis is not a universal fact certificate.

Feedback is governance input, not truth voting. Status lookup reports the lifecycle of an issued analysis without rewriting the historical verdict.

Workflow 7: Content Relationships and independent comparison

Content Relationships compares two exact URLs using stored evidence and conservative states. It does not prove common ownership, coordination, deception, copying intent, or publisher motive.

Exact-URL Evaluate can also expose deterministic comparison evidence where the stored evidence supports a narrow comparison. Explicit abstention is a valid result when alignment or scope requirements are not satisfied.

Workflow 8: Retrieve and verify a text record

curl -sS \
  'https://www.goguides.com/verified-text.php?q=gravity&format=json'

Topic results can contain previews. Follow the direct record URL to obtain the complete normalized text before recomputing the published SHA-256 value.

import hashlib

computed = hashlib.sha256(
    record["verified_text"].encode("utf-8")
).hexdigest()

assert computed == record["hash_sha256"]

Web Bot Auth

Supported signed requests can carry cryptographic machine-identity evidence under the public Web Bot Auth contract. A verified signature establishes control of the signing identity used for that request; it does not establish endorsement, benign intent, citation, training, recommendation, dependency, or commercial use.

Evidence → Interpretation → Decision