RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Uncertain delivery shouldn't mean a second payment

Resume the same privately stored authorization and operation after a timeout. Preserve source, purpose and verified delivery binding.

Why this evidence matters

Resume the same privately stored authorization and operation after a timeout. Preserve source, purpose and verified delivery binding.

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.

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

Current supported buyer integration

Fresh 0.02 USDC; deep 0.05 USDC on Base eip155:8453. Pin the exact recipient, USDC asset, fee and Ed25519 verification key. The adapter verifies offer, report, receipt and delivery binding. Private checkpoint files retain bearer authorizations and are not application-level encrypted; protect them with private ACLs and encrypted storage.

Install, call and verify: complete TS/Python guide Public buyer journey

SIWX adapter recovery

Resume the same operation ID, input and durable private directory. The exact saved payment and SIWX proof are reused; a pending or uncertain operation must not receive a replacement authorization. Checkpoints contain bearer authorizations and are not application-level encrypted. Use private ACLs/encrypted storage; no automatic cleanup is provided. Never reuse an archived operation ID.

Complete configured-client guide

Before any signature

Assign a stable logical request ID. Store credentials/checkpoints outside logs and model context. Stop on mismatched recipient, network, price, signed offer or evidence key.

After ambiguous submission

For the public SIWX flow, call the same adapter again with the same operation ID, input and private directory; it reloads the saved request/payment/SIWX state. The separate legacy quote/claim client resumes its own claim checkpoint. Do not re-quote or invoke the wallet again to clear the error.

A locked or interrupted-before-checkpoint state requires investigation; do not delete the lock or overwrite the state automatically.

When delivery is not verified

Hold ingestion on signature, receipt or binding mismatch. Retain the private checkpoint for recovery. UNKNOWN never becomes permission because a payment succeeded.

Reconciliation has not been repaired in this phase. Manual recovery may be necessary; zero-support operation is an objective, not a demonstrated guarantee.