RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402
From supported URL to verified rights evidence
Start with a free capability read. A fresh report is 0.02 USDC and a deep report is 0.05 USDC as observed; the signed quote controls the exact purchase.
1. Check origin coverage and purpose
GET the current capability list before any quote. Use rights.preflight.v1 only when enabled.
Pass canonical HTTPS URLs without credentials, query, fragment, nonstandard port or encoded slash. Exact origin membership matters.
GET https://api.getacqpath.com/v1/capabilities2. Prepare one quote when evidence is needed
Quotes perform no financial settlement but can fetch metadata and consume quota. Do not create quotes for speculative discovery or every search result.
The example origin is supported at the observation time; this URL is illustrative and has not been shown to yield a purchasable declaration. Keep the returned claim private.
POST https://api.getacqpath.com/v1/rights/quote
Content-Type: application/json
{
"resource": "https://rslstandard.org/",
"purpose": "ai-input",
"user_class": "commercial",
"tier": "fresh",
"max_total_micro": "20000"
}3. Handle unavailable and UNKNOWN
available:false with NO_VERIFIABLE_DECLARATION has no report fee. A discovered but unsupported declaration can produce a purchasable UNKNOWN report. Inspect the preview and decide whether diagnostic evidence is worth buying.
UNKNOWN, missing declarations, unsupported origins and LICENSE_REQUIRED do not authorize use. A report records observed RSL declarations; it is not a license or legal clearance.
4. Buy with bounded, verified authorization
Check live coverage → prepare one bounded quote → inspect availability/preview → verify the signed offer → obtain buyer-controlled payment authorization → persist the encrypted checkpoint → redeem and verify report, receipt and delivery binding. After ambiguity, resume the same checkpoint; never sign a replacement payment blindly.
The buyer-side client pins Base, USDC, recipient and maximum amount; verifies signed offer, report, settlement receipt and delivery binding; and requires durable checkpoint persistence. A verified receipt is not independent blockchain finality.
5. Reuse the integration safely
Use one stable logical purchase ID for one resource/purpose/context request. Resume an existing checkpoint after a timeout. Start a new purchase only for a deliberately new evidence request.
The npm package is unpublished. Use the client source from this repository; no npm install instruction is required.
git clone https://github.com/reflectme-source/acqpath-distribution.git
cd acqpath-distribution
node examples/read-only.mjs