# Webpulser (webpulser.com): agent-readiness 65/100, grade C

> Rank 230 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T00:20:16.195Z. Page: https://qomvia.com/site/webpulser-com  JSON: https://qomvia.com/api/score/webpulser-com

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about Webpulser.com in my knowledge base.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific services provided by Webpulser.com",
    "Their client base and reputation",
    "Their precise market position",
    "Operational details and business model",
    "Their financial performance"
  ],
  "alternatives": [],
  "business": "I do not have information about what this company does.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 23/26
- Discovery surface: 5/20
- Identity & policy: 5/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No llms.txt
- [blocker] No API or feed to read
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No machine-readable contact

## Add-on packs
- E-commerce & product feeds: 15/100 (not part of the public score)

## FAQ
Q: Is Webpulser readable by AI agents?
A: Webpulser (webpulser.com) scores 65 out of 100 for agent readiness, grade C, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright.

Q: What stops agents from using webpulser.com?
A: The heaviest problems are: No llms.txt; No API or feed to read; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.

Q: How is the Webpulser agent-readiness score calculated?
A: Qomvia fetches public pages of webpulser.com as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100. E-commerce & product feeds checks are scored separately (15/100) and do not affect the public score or rank.

Q: How often is this score updated?
A: Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from yesterday, on 29.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard
- Score another site: https://qomvia.com/