A crawler result should carry more than a URL

Why this evidence matters

Attach an observation of machine-readable usage declarations to eligible public-web results without changing crawling behavior or bypassing access controls.

A source URL and event time alone may not preserve what the site exposed at observation time. AcqPath records the result and uncertainty for review, not a licence or legal clearance.

Live source eligibility and trust boundary

LIVE: Secure Preflight and Gateway accept eligible public HTTPS URLs through a signed, public-network-only relay. The four origins in reviewed coverage are independently reviewed sources, not the dynamic eligibility limit. Stock x402 remains reviewed-origins-only. Robots, access restrictions, per-origin quotas and UNKNOWN outcomes still apply.

Attach one field

Keep the existing URL, content and metadata response. Add rightsEvidence containing the provider-neutral resolution for the explicit machine-use purpose.

This is an Attach-mode integration: the consumer can log, display or route on the evidence later. Unsupported sources remain explicit rather than silently allowed.

{
  "url": "https://example.com/article",
  "markdown": "...",
  "rightsEvidence": {
    "schema": "rights-evidence.resolution.v1",
    "status": "resolved",
    "evidence": [{"statement": "license_required"}]
  }
}

Current scale boundary

The public gateway is not an arbitrary-domain high-volume crawler. Today use reviewed coverage and bounded operations. Large embedded crawler volume should move to the future reviewed partner-origin registry + asynchronous batch path rather than weakening SSRF controls.