RSL DECLARATIONS · SIGNED EVIDENCE · HTTP X402

Preflight a URL through one stable HTTP endpoint

Account-free declared-rights evidence for autonomous content use. Start without payment and check client compatibility before spending.

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

1. Discover capability and prepare

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.

Supported paid purposes: ai-input, ai-index, ai-train, search. Start with GET /v1/capabilities. Do not call the disabled acqpath_quote routing tool.

{
  "resource": "https://rslstandard.org/",
  "purpose": "ai-input",
  "tier": "fresh",
  "max_total_micro": "20000"
}

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

2. Inspect the 402

Fresh 0.02 USDC; deep 0.05 USDC. Base mainnet eip155:8453; USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913; recipient 0xf69DBbd053fb0Fbc78ADfdB1BFe3b0D1F57300ec. The verified signed offer is authoritative; paying buys the report, not content rights.

A stranger can inspect the endpoint and prepare a real LICENSE_REQUIRED resource without an AcqPath API key. Preserve X-AcqPath-Request privately. A decoded header is not signature verification.

3. Payment compatibility boundary

Standard x402 v2 uses PAYMENT-REQUIRED, PAYMENT-SIGNATURE and PAYMENT-RESPONSE. After verifying the offer, use the unchanged official signer with the AcqPath SIWX adapter. Legacy nonce-binding support is retained only for existing integrations. Retain identical normalized input and private request context. Do not modify a standard signer nonce after signing. The repository legacy SDK targets quote/claim report URLs and is not a drop-in public endpoint client.

Detailed external buyer contract

4. Successful signed output

The GET contract at the same endpoint describes the JSON schema. Successful paid output contains report, evidence, payment_settlement and delivery_proof. Verify Ed25519 evidence, signed receipt, source/purpose and exact amount/transaction binding before accepting it. Published examples are synthetic; no external paid delivery has yet been proven.

On uncertainty preserve the same checkpoint and request; never generate a second signature. A settlement response is not independent chain finality or duplicate-charge proof.

ALLOW_DECLARED is observed evidence, not permission. DENY_DECLARED and LICENSE_REQUIRED require a hold or applicable license review. UNKNOWN stays UNKNOWN. No legal advice, legal clearance, ownership verification or license acquisition. HTTP 403 is not bypassed.

Examples and workflows

JavaScript and Python examples run only the unpaid HTTP preparation; TypeScript maps RAG, crawler, research, training and search workflows. Configured official-client integrations are documented below; generic zero-config buyers remain unsupported on the secure SIWX endpoint; use the separate fixed fresh stock endpoint for tested stock clients.

JavaScript Python TypeScript workflow gates MCP connection

Copy-paste TypeScript / Node integration

Inject your configured buyer signer; allowPayment defaults to false.

import { createAcqPathFetch, privateFileStore } from './acqpath.mjs';

// Inject an existing buyer-controlled viem EOA signer. No key is stored here.
export async function preflight({ signer, operationId, input, privateDirectory, allowPayment = false }) {
  const buy = createAcqPathFetch({
    signer, expected: {"origin":"https://api.getacqpath.com","network":"eip155:8453","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","payTo":"0xf69DBbd053fb0Fbc78ADfdB1BFe3b0D1F57300ec","amount":"20000"},
    publicJwk: {"key_ops":["verify"],"ext":true,"alg":"Ed25519","crv":"Ed25519","x":"PzeeZ8d8Np85ix9ialbrLZz9ebY_Og72dScn1IAft6M","kty":"OKP"},
    store: privateFileStore(privateDirectory), allowPayment,
  });
  return buy('https://api.getacqpath.com/v1/rights/preflight', {
    method: 'POST', operationId, body: JSON.stringify(input),
  });
}

Copy-paste Python integration

Inject your existing buyer account; no seller secrets or AcqPath account required.

from acqpath_httpx import AcqPathClient, PrivateFileStore

# Inject an existing buyer-controlled eth_account LocalAccount.
async def preflight(account, operation_id, input, private_directory, allow_payment=False):
    buyer = AcqPathClient(
        signer=account, expected={"origin":"https://api.getacqpath.com","network":"eip155:8453","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","payTo":"0xf69DBbd053fb0Fbc78ADfdB1BFe3b0D1F57300ec","amount":"20000"},
        public_jwk={"kty":"OKP","crv":"Ed25519","x":"PzeeZ8d8Np85ix9ialbrLZz9ebY_Og72dScn1IAft6M"},
        store=PrivateFileStore(private_directory), allow_payment=allow_payment,
    )
    try:
        return await buyer.post('https://api.getacqpath.com/v1/rights/preflight',
                                json=input, operation_id=operation_id)
    finally:
        await buyer.aclose()

Pinned dependencies, delivery verification and retry

Install the supplied pinned Node manifest or Python requirements with the source adapter. The complete guide includes installation, a call using your existing buyer account, response handling and exact same-operation recovery. No internal design document is needed.

External revenue remains 0 USDC in the verified baseline. A configured buyer is technically supported; the absence of a real external paid E2E is an evidence limitation, not a technical payment block.

Complete installation and verified-response examples