Settled Connect agent

Privacy policy

Last updated 2026-10-07. This covers everything Settled runs: the website at settled.tools, the HTTP API and the MCP server (/mcp and /mcp/free), the settled-x402 npm package and agent skill, the Claude plugin, the Discord and X bots, and the crawlers described on our crawlers. Settled has no user accounts, sets no cookies, shows no ads, and does not sell or share data about who uses it. Scores are never for sale.

What Settled collects, by what you do

Visiting the site

Settled is hosted on Cloudflare. Cloudflare keeps request logs for the service (the IP address the request came from, the path and query string requested, the user agent, the response status) for up to 7 days; we read them to debug problems. Page views are counted with Cloudflare Web Analytics, which uses no cookies and no fingerprinting. Nothing is stored in your browser, except by the monitor page, which only an administrator uses.

Calling the API or the MCP server

Paying for something

Paid routes settle over x402 in USDC on Base. A payment is a public blockchain transaction, and Settled records what it can read from one: the paying wallet address, the amount, the transaction hash and what was bought. Payments are verified and settled by Coinbase's x402 facilitator, which receives the signed payment payload. A day pass is a signed token; Settled does not store it, so it cannot be looked up later. A Watchdog stores the endpoint it watches, the paying wallet, and the webhook URL you gave, and sends signed alerts to that webhook until the watch expires. Settled never holds, custodies or moves your funds, and never asks for a private key.

Discord and X

Settled's bots post aggregate figures to the Discord server and to @settledfyi. They never name an individual seller, buyer or wallet. The Discord server itself is run by Discord under its own policy; Settled keeps no member data beyond what Discord shows us.

The npm package, the skill and the plugin

settled-x402 sends Settled only the origin and path of the endpoint an agent is about to pay (and, for the search action, the keywords, network and price limit). Keys, payment payloads and request bodies are never sent, and local or private addresses are never sent. The skill and the plugin make the same calls over HTTP or MCP; nothing runs on your machine except the optional settled_check.py script, which calls the free check.

Who processes data for Settled

Settled reads public blockchain data (USDC transfers on Base, ERC-8004 registrations) from public nodes and explorers. That data is public by design and is not personal data Settled collected from you.

How long things are kept

DataKept
Cloudflare request logsUp to 7 days
Daily quota counters (hashed client)7 days
What-gets-checked counters (per target, no client)30 days
Submission log (URL, time, hashed IP)30 days
The index: endpoints, probes, scout purchases, on-chain payment records, venue measurementsAs long as Settled runs; it is the product, and daily signed snapshots keep its history provable
Seller claimsUntil the seller removes them
Watchdogs and their alertsThrough the watch and its renewals; ask to have an expired watch deleted
ReportsAs long as the endpoint is in the index
Backups of the databaseDated copies kept by the operator, for recovery

Your choices

Settled is not directed at children, and nothing on it is meant for anyone under 18. If this page changes, the date at the top changes with it, and the previous wording stays in the site's public history.

Machine-readable: llms.txt · openapi.json · our crawlers