What may be logged
Primitive402 may log route name, method, status code, latency, charged status, price metadata, user agent, request id, error code, and timestamp for operations and abuse prevention.
For x402 payment operations, Primitive402 may log payment metadata such as transaction hash, payer wallet if available, route, response status, request id, and timestamp. Primitive402 should never log private keys, seed phrases, admin tokens, or secrets.
Usage logs use hashes for request bodies, response bodies, IP addresses, and target domains. For URL-based tools, the submitted public URL may be fetched to run the requested tool, but metrics store a hash of the target domain instead of the raw hostname.
Fetched public pages
URL-fetching tools are intended for public HTTP or HTTPS pages. Primitive402 may fetch, truncate, parse, hash, and analyze public page content to produce structured JSON, snippets, page metadata, confidence scores, or proof artifacts.
Do not submit private, authenticated, internal, or sensitive URLs. Do not submit wallet keys, admin tokens, seed phrases, credentials, customer data, or other secrets.
Public beta
Primitive402 is in public beta. Logging, retention, product behavior, x402 payment setup, and documentation may change during the production mainnet billing beta.