RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Integrate source-rights evidence without rebuilding your tools

Preserve observable declarations and uncertainty alongside the URL your web agents, crawlers or RAG pipelines already process.

What changes after integration?

Before: your tool returns a URL and content, while source-rights declarations at observation time may be missing from the record.

After: the same tool still runs; a separate provider-neutral record can identify the resource and intended use and retain verified rights evidence with a timestamp and source reference.

Example only. A missing declaration, UNKNOWN or provider outage does not mean content use is authorized.

Read the neutral resolution schema

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.

Current production capabilities Eligible URL and reviewed coverage

Purpose for URL-bearing tools without user intent

A partner may explicitly configure ai-input as a deployment-level shadow default. Mark the resulting purpose_source as configured_default in the audit context. Never infer user intent from a tool name or override a malformed explicit purpose.

The tool continues unchanged in Observe mode. AcqPath provides evidence, not a policy verdict; real paid evidence requires customer-controlled x402 authorization and budget limits.

Partner Observe adapter reference

Architecture

AcqPath is the external evidence provider. Your existing gateway, crawler, ingestion layer or policy engine remains the execution and enforcement owner.

Agent / Crawler / RAG
        ↓
AcqPath Evidence Bridge
        ↓
rights-evidence.resolution.v1
        ↓
Your audit / policy engine / metadata

Evidence Bridge README Resolution schema

Copy-paste patterns

Use the smallest adapter matching the existing architecture. The partner-specific work should be field mapping, not a new policy engine.

Gateway shadow Crawler enrichment RAG ingestion metadata Policy-engine input

30-minute technical path

0–5 min: read live capabilities and choose intended purpose. 5–15 min: wire Evidence Bridge to the existing buyer flow. 15–25 min: write shadow events to the local audit stream. 25–30 min: send the first eligible event and confirm a verified evidence_ref or an explicit unsupported/unavailable state.

Then start the local Proof Sprint watcher. It monitors the partner-owned NDJSON stream and automatically prints the commercial verdict; raw URLs do not need to leave the partner environment.

Proof Sprint Live capabilities

Security boundary

Pin the evidence verification key and exact payment terms. Keep claims, signatures, checkpoint data and recovery state private. Do not put them in prompts, analytics, support tickets or logs.

AcqPath reports observed declarations. It does not establish publisher ownership, grant a license or provide legal clearance.

Production limits you should design around

Dynamic HTTPS eligibility is live on Secure Preflight and Gateway with bounded global/per-origin quotas. The four reviewed origin entries remain a separate set, and Stock x402 retains only those four. Do not promise universal crawl access or report availability.

Integrations require backpressure, a stable operation identity, private recovery checkpoints and customer-authorized payment budget. API-key billing, subscriptions and invoices are not active. See the portable Observe adapter.

Observe adapter and fixtures