Privacy
AIPayGen is built for software agents, so it collects as little as it can. No accounts, no cookies, no ad trackers, and nothing is sold.
What a tool call sends where
Your input is used to answer the call and is not written to our database. Most tools forward it to the public source they need (for example DNS over HTTPS, RDAP registries, Certificate Transparency logs, MET Norway weather, OpenStreetMap, CoinGecko, Wikipedia or the web page you name). AI tools run on Cloudflare Workers AI. Answers may be cached at Cloudflare's edge, keyed by the input, so a repeat call is fast: minutes for live data, up to 30 days for reference data that rarely changes.
What we store, and for how long
- API keys: only a hash of the key, its first characters, its credit balance and credit history. Kept while the key exists.
- Usage records: which tool, the price, how it was paid (key id or paying wallet, and the on-chain transaction), success and duration. Never the input or the answer.
- Search text: words typed into marketplace search and find_tool, with the number of results, to learn what agents need. No IP, key or wallet is attached. Deleted after 90 days.
- Free-call counters: a daily count per hashed IP address (never the address itself), to apply the free daily allowance. Deleted after 2 days.
- Payment replay guards: a hash of each x402 payment, so it can't be used twice. Deleted after 7 days.
- Facilitator settlements: for merchants using our facilitator, the merchant's key id, payer and payee wallets, amount and transaction. These are already public on the blockchain.
- Agent listings: the public agent card URL and card contents you submit with register_agent.
Payments
x402 payments go straight from the payer's wallet to ours on-chain. We never hold anyone else's funds or private keys.
Hosting and questions
The service runs on Cloudflare. For questions or deletion requests, open an issue on GitHub.