What AcqPath processes.
What it does not promise.
This statement describes the deployed source-rights observation path for integrators evaluating AcqPath. It is a technical disclosure, not a signed data processing agreement, a regional hosting guarantee or legal advice. Our privacy notice and terms also apply.
AcqPath receives a public resource URL and an explicit intended purpose, inspects bounded public metadata, and prepares signed evidence. It does not need customer prompts, webpage credentials or API keys to check a public source. Sensitive, nonpublic or personal-information-bearing URLs must not be submitted. The system does not make legal-clearance decisions.
Inputs and source disclosure
| Information | Reason and handling |
|---|---|
| Canonical public HTTPS URL, including path | Identifies the resource to inspect; may be included in private prepared reports, signed evidence, and outbound HTTPS requests to the source host. |
| Intended purpose and optional usage context | Binds the observation to a declared AI use, user class and geography. A configured default must be explicit and marked as such by the integration. |
| Public robots/RSL/license metadata | Bounded inspection with public-only DNS/TLS restrictions. Applicable source servers observe these HTTP requests. |
| Payment authorization and settlement metadata | Needed to verify Base USDC payment, reconcile outcome and prevent duplicated settlement. Wallet transaction data may be public on-chain. |
| Operational usage metrics | Decision class, durations, fetch counts, quota and conversion signals; not customer prompts or raw private credentials. |
The API rejects query strings, fragments, embedded URL credentials, unsupported ports and private-address targets. It is not a browser, arbitrary content proxy, web crawler, or mechanism for bypassing access controls. Source websites may log requests independently under their own policies.
Data flow and processing location
Inbound public API requests are handled by Cloudflare Workers. Dynamic public metadata fetching uses a separately authenticated, HMAC-signed Railway relay with DNS/public-IP checks and pinned TLS. At this publication date the Railway relay is deployed in the sfo region (United States); Cloudflare's global network, D1/R2 storage, and the payment facilitator have separate processing characteristics. The precise residence and international-transfer terms of every subsystem have not been certified as EU-only.
Signed report preparation uses application state in Cloudflare Durable Objects and configured private evidence storage. The source URL can form part of the signed evidence and the private payment journal. Public blockchain transactions are not controlled by AcqPath.
Retention
Current default report retention is 30 days after report creation, subject to configured storage lifecycle and removal jobs. Source metadata caches have bounded TTL and respect applicable Cache-Control: no-store or private restrictions when storing snapshots. A no-store source response is not retained as a raw RSL snapshot.
Transient prepared reports and payment-intent objects have their own lifecycle; settlement, reconciliation, and financial journal records are maintained separately as necessary for payment integrity and applicable accounting obligations. Accordingly, a 30-day report-retention setting does not mean all operational or financial records are erased at 30 days. No per-request deletion SLA is represented here.
Payment and access boundaries
Today the public purchasing route uses x402 on Base USDC. Stock x402 is a distinct, reviewed-origins-only compatibility route; Secure Preflight handles dynamically eligible public HTTPS. The signed offer discloses exact terms before payment; a network outage without a meaningful observation must not be sold as a completed Preflight diagnostic.
AcqPath keeps existing authenticated operator access, financial reservation and nonces separate from content-use evidence. Integrations must protect signed authorizations, private request bindings, payment checkpoints and internal credentials. A positive declaration is not a license or an application policy decision.
Partner integration guidance
Use the minimum necessary context: a public URL, explicit or deployment-configured purpose and stable operation identity. Keep the resolver in observe-only mode until the customer independently sets its enforcement policy. Pass only a verified evidence reference/digest into a downstream audit record; avoid exposing full private payment or source details in model prompts or analytics.
If your procurement process requires a signed DPA, a contractual processing location, subprocessor assurances or a deletion SLA, those terms require separate review and agreement. This document does not assert that such contracts are already in place.
Requests and follow-up
For questions about processing, deletion requests or regional commitments, contact the service operator through your established business channel. Do not send credentials, wallet secrets, payment signatures or private source URLs in email. For system availability see service status; for the current technical scope see live capabilities.