RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Connect AcqPath: RSL evidence before ingestion

You arrived through mcp-registry. Connect the remote MCP endpoint, then use a bounded buyer-side HTTP payment integration when a report is needed.

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.

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.

Gateway limits, prices and workflow Complete TypeScript and Python examples

Start with capabilities

MCP: https://api.getacqpath.com/mcp

Fresh 0.02 USDC; deep 0.05 USDC as observed. Quotes perform no settlement. Paid report delivery uses HTTP x402.

{
  "mcpServers": {
    "acqpath": {
      "url": "https://api.getacqpath.com/mcp"
    }
  }
}

Complete quickstart MCP setup JavaScript adapter

Attribution boundary

This page identifies a documentation entry path only. It does not prove that a visitor came from that catalog, integrated successfully, created a quote or paid.

Browser analytics cannot measure all autonomous clients. No referral or wallet identifier is sent to the production API.