Clear limits are part of the product

Evidence you can
reason about.

Public data, bounded execution

Fresh402 fetches public HTTPS documents without running page JavaScript. The secure Node gateway validates DNS results, pins the actual public peer, validates the TLS hostname and rechecks redirect destinations. DNS-over-HTTPS checks alone are not presented as eliminating time-of-check/time-of-use races. Private, local, reserved and service-internal destinations are forbidden. The system does not bypass authentication, protected content or source restrictions.

Explicit payment and durable recovery

A discovery response or payment challenge is not a payment. x402 and MPP require an explicitly authorized native USDC payment on Base. Prepaid calls atomically reserve integer credits and retain durable outcomes. Failed reserved execution releases credits under the documented rules; uncertain settlement must be recovered using original evidence rather than replaced. Purchased credits do not expire. Never share seed phrases, private keys or payment proofs with support.

Free access has its own boundary

Baseline registration is free within existing rate and fetch budgets. The local demo is an illustrative offline example. Authenticated trials remain a separately gated pilot: wallet ownership plus human verification, one-time quotas, network and global rate limits, one concurrent trial operation, a bounded result journal and a finite runtime allocation within the existing grant. The separate machine trial uses an exact EIP-191 wallet-control message without human CAPTCHA, under its own network/global admission and finite shared work/RPC caps. Trial keys cannot authorize purchases. Disabled products have no active free calls.

Privacy without tracking scripts

The website loads its assets from Fresh402 and has no third-party analytics or advertising pixels. Aggregate API telemetry distinguishes technical monitoring, discovery, challenges and actual successful operations. A 402 count is not revenue. Trial identity and network identifiers are keyed hashes; credentials are stored as verifiers. Operational and financial records remain private. Human verification on the trial page uses Cloudflare Turnstile. Read the approved privacy notice for customer terms.

Capacity and availability

Finite response, input, concurrency, daily-use and runtime budgets apply. A 429 or temporary upstream failure is possible even when an account has credits or trial quota. Monitoring does not provide an uptime guarantee. Sources may change between observations; snapshots and bounded diffs do not establish legal compliance, token safety or universal semantic compatibility.

Report a concrete issue

Support and billing: fresh402@proton.me. Do not include credentials, seed phrases, private page contents or payment signatures. The public repository contains client documentation; the backend source and operational reports are private.