RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

From a source URL to a verifiable rights observation

Record what an eligible public HTTPS source declares for the intended use, review the exact purchase terms, and verify the evidence before attaching it to your existing workflow.

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

Separate stock marketplace endpoint

SUPPORTED SECURE MODE: tested official TypeScript/Node x402 2.25.0 and Python x402 2.22.0 with the AcqPath SIWX adapter on /v1/rights/preflight; unchanged signer and random nonce, recommended when payer-signed request binding is required. SUPPORTED STOCK WIRE MODE: the same official stock clients without SIWX, custom nonce, signer or buyer hook on /v1/rights/preflight/x402, fresh only, 0.02 USDC. Stock binds one request atomically at first valid use; it does not sign the POST body in advance. Zero-config compatibility outside this fixed stock endpoint, stock SIWX-only hooks, Payments MCP and generic paid proxies are not supported by this integration.

Same signed authorization plus same normalized request recovers the existing stock result; changed input or another route is rejected after binding. A pre-use leaked stock authorization can be raced for another same-priced request. Keep signed HTTP requests private. Never create a replacement authorization after an uncertain payment.

Stock endpoint, JSON, official TypeScript/Python and recovery

Rights Gateway: select the paid operation

LIVE Base USDC pricing: Secure Preflight 0.02 fresh / 0.05 deep per prepared settled report; Ingestion Gate 0.04 + 0.02 per distinct URL fresh or 0.06 + 0.04 per URL deep (1–4 eligible public HTTPS URLs); Revalidation 0.03 fresh / 0.06 deep. Stock x402 stays fresh-only 0.02 and reviewed-only. No new subscription, prepaid, API-key billing or invoicing plan is active.

A Secure Preflight may offer a disclosed paid UNKNOWN or no-declaration diagnostic after meaningful public-source observation. An outage with no usable source observation, invalid URL or exhausted safety budget is not billable Preflight. Gateway pricing covers a bounded observation attempt after verified authorization. UNKNOWN never authorizes content use.

Gateway limits, prices and workflow Complete TypeScript and Python examples

Start with the stable public endpoint

POST https://api.getacqpath.com/v1/rights/preflight with {resource,purpose,tier:"fresh",max_total_micro:"20000"}. A prepared 402 includes price/network/asset and the required private request binding. Empty POST is discovery-only. HTTP 200 with available:false and charge_micro:"0" is not a purchased report. There is no AcqPath account, API key or operator token.

Public buyer journey

Official TypeScript / Node and Python integration

Add the AcqPath transport adapter, independently pinned service terms/key, private durable store, explicit buyer opt-in and stable operation ID. It adds one unsigned prebinding round trip and one official SIWX signature; the stock payment signer is unchanged.

Use the same operation ID, body and store after response loss. Never replace a pending authorization. EOA only; private-store retention and Python canonical-input limits are explained in the guide.

Complete configured-client guide TypeScript / Node adapter Node integration example Pinned Node manifest Python adapter Python integration example Pinned Python requirements

1. Check eligibility and declare purpose

Read /v1/capabilities. coverage_mode=PUBLIC_HTTPS_DYNAMIC_WITH_SAFETY_GATE and dynamic_public_https=true distinguish eligible public HTTPS from reviewed origins. Stock x402 remains reviewed-only.

Supply the intended purpose explicitly (ai-input, ai-index, ai-train or search). Use deployment defaults only when configured by the owning partner for Observe. Query, credentials, fragments, private IPs and nonstandard ports are rejected.

GET https://api.getacqpath.com/v1/capabilities

Read-only JavaScript example Read-only Python example

2. Prepare and buy through the supported adapter

Check live coverage → call POST /v1/rights/preflight through the AcqPath SIWX adapter → verify the prepared signed offer → preserve the unchanged official payment authorization privately → complete SIWX prebinding/authorization → receive the verified report. Use the same operation ID, input and private store after ambiguity; never create a replacement payment.

A selected real resource can consume metadata quota even before payment. Reuse one stable operation ID. The prepared 402 binds this input; an empty POST only describes the service. The guide includes exact dependency installation and calls with your existing buyer-controlled EOA signer.

Copy-paste TS/Python instructions

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. 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.

AcqPath adapters are supplied as source, not published npm/PyPI packages. Install their pinned official dependencies and follow the configured-client guide.

git clone https://github.com/reflectme-source/acqpath-distribution.git
cd acqpath-distribution
node examples/read-only.mjs

Source repository Recovery decisions

Existing legacy integrations

The quote → private claim → report URL SDK remains available for existing users. New integrations use the public SIWX adapter above; no custom payment nonce is needed.

Legacy source example