How we watch services
For providers who want their service represented accurately here. There is nothing to buy and no way to pay for position. Accurate public metadata is the whole game.
What We Read
- openapi.json at your domain root: your name, description, logo, and per-route details come from it. Served as real JSON with HTTP 200, not an HTML app shell.
- llms.txt and robots.txt: read daily for change detection and agent-access policy.
- Pricing and status pages: change-watched. A published status JSON API (statuspage.io style) gives cleaner signals than an HTML status app.
- MCP endpoints: liveness on the fast tier; tool schemas where the server answers without credentials.
- x402 endpoints: the monitor observes your free 402 challenge. It parses price and payTo from the challenge and tracks drift. It never pays.
What Improves Your Row
- Serve real JSON at /openapi.json (a 200 HTML shell records as a soft-404).
- Keep your 402 challenge parseable against the x402 spec: that is what the to-spec check reads.
- A logo URL in your OpenAPI info block replaces the grey initial tile.
- Ordering is alphabetical with measured-column sorting. There is no rank to buy and no usage-based ordering.
Corrections
If a number about your service looks wrong, dispute it: contact@agenticresourceradar.com. We respond publicly and release the underlying observations. See the governance page.