Settled Connect agent

Privacy policy

Last updated 2026-10-15 (the unsubscribe list for seller emails). 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. Since 2026-10-13 Settled has Cloudflare's per-request invocation logs turned off, because they also kept request header values, where x401 proofs and day passes travel; Settled's own logs record what its jobs and checks did, not request headers or bodies. 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

Trial links

A free trial link (settled.tools/t/…) gives a download of the index export and counts how it is used. For each visit Settled records the time, whether it came from a browser, a script or a link-preview bot (and which one, such as Discord's), the name of the site that sent the visitor when the browser says, and a truncated hash of the IP address, so visitors can be counted per link without keeping the address. Nobody is asked who they are. These records are deleted after 30 days; the link keeps only its totals. An export bought from a trial link's page notes which link it came from.

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 keeps its id, expiry and the paying wallet, not the token itself, so a lost pass cannot be shown again. 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. An index export keeps the paying wallet, when its download link expires and how many times it was downloaded; the link itself is a signed token that Settled does not store. Settled never holds, custodies or moves your funds, and never asks for a private key.

Paying a seller in the index

Settled's ledger reads public USDC payments on Base to the sellers in its index, whoever makes them. For each wallet that pays one, Settled keeps the first and last day it saw a payment, and each night it writes a 30-day summary: the days with a payment, the amount paid and the number of sellers paid (counting only independent sellers), and whether the wallet is on the sanctions list or in a circular flow. This measures how agents pay. Nothing about the person behind a wallet is involved, and nothing is published per wallet. The first and last days are deleted after 180 days without a payment; the summary is replaced every night and removed once a wallet has gone 30 days without one.

Payer records

A wallet's owner can ask Settled to sign a payer record (/v1/credentials/payer): a credential stating facts from that 30-day summary, issued only after the wallet itself signs the request. Settled hands the credential to whoever asked and does not keep it. It keeps a row per record: the wallet, a fingerprint of the key the record is bound to, when it was issued and expires, the facts it states, and whether and why it was revoked. From January 11, 2027 a record is paid for over x402, and the row also holds the wallet that paid and the price (often the same wallet, but an operator can pay for its agents' wallets). A record's slot on the public status list shows only whether that record was revoked, not whose it is. The owner can revoke their records at any time (/v1/credentials/payer/revoke), and Settled revokes them when the wallet turns up in a circular flow or on the sanctions list. A seller that checks a record does so offline, so Settled does not learn who was shown what; a seller that uses /v1/credentials/verify instead sends Settled that presentation, and Settled keeps nothing from it. On Settled's own free tier a shown record is traded for a signed token that lasts an hour; tokens and presentations are not stored.

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, per tool)7 days
Endpoint-search counters per day pass7 days
Trial link visits (time, browser or script, referring site, hashed IP)30 days
Index export sales (wallet, link expiry, downloads)As long as Settled runs, like other payment records
What-gets-checked counters (per target, no client)30 days
Submission log (URL, time, hashed IP)30 days
Payment summary per paying wallet (last 30 days)Replaced every night; removed after 30 days without a payment
First and last payment day per paying walletUntil 180 days without a payment
Payer records issued (wallet, key fingerprint, dates, facts stated, revocation; from 2027-01-11 also the paying wallet and price)30 days after the record expires
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
Email unsubscribe list (address, date, link or one-click)As long as Settled runs, so the request is honoured
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