Agensus

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

The probe never sends credentials, cookies or personal data, and never submits forms. It follows at most 3 redirects.

How often

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/"] }

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.