Privacy policy

Agent402 (agent402.tools) — last updated 2026-06-12.

Agent402 has no accounts, no signups, no cookies, and no analytics or ad trackers. The entire server is open source, so every claim below is verifiable in code.

What we process, and why

• Tool inputs. The data you send to a tool (text to hash, a URL to render, …) is processed in memory to compute the response and is not stored — with one deliberate exception: the /api/memory tools, whose purpose is storage (see below).
• IP addresses. Used for free-tier rate limiting (kept in process memory for up to one hour) and in standard, short-lived operational logs (request path, status code) for abuse prevention and debugging.
• Payments. We never see card numbers, names, or emails — there are none. Payments settle in USDC on the public Base blockchain via the x402 protocol; wallet addresses, amounts, and timestamps are public on-chain by the protocol's design, not collected by us. Payment verification is performed by the payment facilitator (Coinbase CDP).
• Memory tools. Data written via /api/memory is stored on our server keyed to the paying wallet, readable only by that wallet (or wallets it explicitly grants), until the owner deletes it or its TTL expires. A tamper-evident audit log of accesses is kept for the namespace owner.

Third parties

• Tools that fetch external URLs (extract, render, screenshot, …) contact those sites from our server with the URL you provided.
• /api/search forwards the query to the Brave Search API to produce results.
• Hosting is on Railway. On-chain settlement is on Base (Coinbase CDP facilitator).
• We do not sell or share data with anyone for advertising or any other purpose.

The MCP connector (https://agent402.tools/mcp)

The hosted connector is anonymous: requests carry no identity beyond the connecting IP, which is used only for rate limiting as described above. Tool calls made through it are processed exactly like the HTTP API.

Retention

Operational logs are short-lived (platform default, days not months). Rate-limit counters live in process memory only. Memory-tool data persists until deleted by its owner or TTL expiry. Aggregate, non-personal counters (total calls served per tool) are kept for the public /api/stats page.

Contact

Mikey Petrillo — GitHub issues or github.com/MikeyPetrillo.

← agent402.tools