The Agensus probe
Agensus keeps a neutral record of the services AI agents depend on: MCP servers, A2A agents and x402 paid endpoints. To build it, our probe makes a few small, read-only requests to public endpoints found in public registries and discovery lists. It records whether they answer, and what they say they offer.
Agensus is in an observation phase. Results are not published yet.
Who runs it
Agensus is operated by Pa Luna LLC. Contact: security@agensus.net, also listed in /.well-known/security.txt.
How to recognize it
Every request carries this User-Agent:
Agensus-Probe/0.1 (+https://agensus.net/probe; opt-out: /.well-known/agensus.json)
MCP requests also name the client Agensus-Probe, with a link to this page. Requests come from Google Cloud in the United States. The addresses aren't fixed, so please recognize the probe by its User-Agent.
What it sends
- MCP servers: a discovery or initialize request, then a request for the tool list. It closes any session it opened. If the server requires sign-in, it reads the public OAuth metadata. It never calls a tool.
- A2A agents: one request for the agent card at
/.well-known/agent-card.json, or the older/.well-known/agent.json. - x402 endpoints: one GET to read the
402 Payment Requiredanswer. If the endpoint's listing says POST, it sends a POST with an empty JSON body. It never pays and never sends a payment. - Your policy file:
/.well-known/agensus.json, at most once a day per host (see below).
The probe never sends credentials, cookies or personal data, and never submits forms. It follows at most 3 redirects.
How often
- About once a day per endpoint. An endpoint that keeps failing is checked less often.
- At most 1 request at a time per host, at least 10 seconds apart.
- At most 4 requests at a time per IP address, for shared hosting.
- Each request stops after 10 seconds and reads at most 256 KiB.
How to opt out
Publish /.well-known/agensus.json on your host. To opt out the whole host:
{ "optOut": true }
To opt out only some paths, list their prefixes:
{ "optOut": ["/mcp", "/paid/"] }
- When it takes effect: we read the file before probing your host, at most once a day, so a new opt-out takes effect within a day.
- When in doubt, we honor it. A rule we can't read opts out the whole host. If the file is briefly unreachable, an existing opt-out stays in force.
- To opt back in, remove the rule or set
"optOut": false. - If you can't publish a file, email security@agensus.net from an address at your domain, and we'll stop probing the host.
What we keep
For each request we keep the answer's status and timing, plus the public metadata the endpoint returned: tool lists, agent cards, and payment terms (price, payee, network). Detailed results are kept for 30 days, then archived for 12 months; the history of changes is kept longer. We don't store credentials or query strings found in URLs.