Terms of use

Pay per call

Each paid call is one purchase at the price on /pricing. The amount in the HTTP 402 challenge at call time is the price you pay. There are no accounts, subscriptions or API keys.

An x402 payment is settled only when the endpoint returns a successful (2xx) response. Unpaid calls get 402. Invalid input (4xx) and server errors (5xx) are not settled, so you are not charged for them.

Card payments (Stripe): one checkout buys one call. Checkout charges the listed price or $0.50, whichever is higher. The call runs after Stripe confirms the payment.

No refunds on delivered results

A 2xx response is a delivered result and is not refunded. That includes a 2xx that is empty or partial and says why in a reason field, for example: seo could not fetch the page, research found no sources, osint-graph found no match. x402 payments are on-chain USDC transfers and cannot be reversed by us.

If you were charged for a call that did not return 2xx, email [email protected] with the transaction hash.

Your inputs are not stored

We do not store request bodies. The service does not write your inputs to its database or to its logs. For each paid call it keeps one ledger row: skill id, path, price, payment status and time. Our host (Vercel) keeps standard request logs (path, status, time, IP address). Inputs travel in POST bodies, which are not in those logs.

Where your input does leave this service:

• Skills that fetch the web send what you give them to the sites they read: seo and ai-detector (with a url) fetch that URL; research sends your query to Wikipedia, Hacker News and DuckDuckGo; osint-graph sends the name to Wikidata; url-to-markdown fetches that URL (and its robots.txt).
• token-risk sends the token address to public Base RPC endpoints (mainnet.base.org, publicnode.com, drpc.org) as read-only calls. Nothing is signed or sent on-chain.
• research and ai-detector can also send the query or text to OpenRouter, an LLM API, when that option is turned on for the server.
• Card checkout: your input is saved in the Stripe Checkout Session so the call can run after payment, and Stripe keeps it under its own policies. The result is kept briefly on the server instance so a page reload or webhook retry does not run the call twice.

The deterministic utilities (for example pii-redact, csv-normalize, base64, sha256, json-*) run in memory and call nothing else.

No warranty

Results are automated and provided as is. Heuristic skills (ai-detector, seo score, research, pii-redact's pattern matching, token-risk) can be wrong. Check results before you rely on them. Use public-data skills lawfully and within the source sites' terms.

Changes

Prices and these terms can change. The 402 challenge at the time of your call is authoritative for price.