RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Partner Integration Kit

Architecture, evidence schema, shadow patterns and copy-paste adapters for a 30-minute AcqPath partner integration.

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 run the first 100 events and produce the local shadow report.

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

Current public coverage is explicit and reviewed. The public Ingestion Gate accepts at most four unique reviewed URLs. Use current capabilities and OpenAPI as the source of truth.

Do not design a high-volume integration around arbitrary unreviewed URLs. The scale path requires partner-scoped origin eligibility and asynchronous batch semantics.