AIPayGenBot
Saw AIPayGenBot in your logs? Your API, MCP server or site is probably listed in the AIPayGen marketplace, where AI agents look for tools to use. The bot checks that listings still work, so agents aren't sent to dead ones.
What it does
| Request | Why | How often |
|---|---|---|
MCP servers: one tools/list call | Confirms the server answers and has tools | About every one to two days per listing |
| x402 endpoints: one unpaid request | Reads your 402 price quote so agents see the right price. It never pays and never sends a payment. | About every one to two days per listing |
| Other APIs: one request to the listed URL | Checks that something answers there | About every one to two days per listing |
Agent cards (/.well-known/agent-card.json) | Keeps agents' listings up to date | About once a day, only for agents listed from their card |
Agent-card discovery: your robots.txt, then /.well-known/agent-card.json (/.well-known/agent.json only after a 404) | Finds an A2A agent on a site already listed, so other agents can find it too. A robots.txt rule for AIPayGenBot, or an email, opts your site out. | At most once a month per site, every 3 months after a refusal |
Your robots.txt and home page | Only when someone runs the free AI crawler check on your site. The home page request names GPTBot in its user agent (checking GPTBot access) so it is answered the way your rules answer GPTBot; it never claims to be OpenAI. | Once per check, cached for an hour |
How we tell real AI crawlers from fakes
Agents that sign requests with Web Bot Auth are verified by signature; others by their company's published IP ranges. A scraper made to look like a person can't be told apart from one, and we don't claim to.
See exactly what we see for your own request at /bot/check. Try it with a fake user agent: this comes back "verdict":"fake", because the request isn't from OpenAI's addresses.
curl -A "GPTBot/1.2" https://aipaygen.com/bot/checkRun a website?
If AIPayGenBot checked your site, someone looked up which AI crawlers can read it. Run the same check yourself, free. To see which AI crawlers actually visit and what they would pay, start the free AI crawler report: no wallet needed, every page keeps loading for everyone, and you can charge AI crawlers per page later if you want.
It sends no credentials and no personal data, and a timeout of a few seconds keeps each check light. After three failed checks in a row, a listing is hidden from search until it answers again.
Full user agent: AIPayGenBot/2.1 (+https://aipaygen.com/bot). It runs on Cloudflare Workers, so requests come from Cloudflare's shared addresses rather than a fixed IP list.
If you run the API that was checked
Agents found your listing here. You can make more of that:
- Get paid per call. Put your API behind the AIPayGen gateway and agents pay you per request in USDC over x402, straight to your wallet, with no accounts or API keys to hand out. How it works.
- See how agents find you. Search the marketplace for your API's name to see your listing, its health and its price.
- Show it's listed. Every listing page has a badge for your README with live health from these checks, so agents and developers can find you.
- Charge AI crawlers. If AI crawlers read your docs or pages, pay-per-crawl answers them with a price instead of a free page. You can also verify a bot from your logs.
Stop the checks or remove a listing
Email hello@aipaygen.com with the URL, and we'll remove the listing and stop checking it. Listings come from public sources (the official MCP Registry, x402 discovery feeds, Hugging Face Spaces, Smithery's skill registry and LocalMark's A2A directory, whose data is credited "Data: LocalMark (localmark.ai), CC BY 4.0") or from their owners.