# Weflair (weflair.com): agent-readiness 49/100, grade D

> Rank 717 of 1000 on Qomvia (rubric v2.2.1). Last scanned 2026-09-23T20:30:17.215Z. Page: https://qomvia.com/site/weflair-com  JSON: https://qomvia.com/api/score/weflair-com

## Summary

{
  "known": false,
  "confidence": "high",
  "summary": "I do not have sufficient pre-existing information about weflair.com to provide a summary of its operations or purpose. My knowledge base does not contain specific details regarding this domain.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The historical usage or content of the domain",
    "Any services or products previously offered under this domain name",
    "The reason for the domain being listed for sale",
    "The intended target audience for any potential future development",
    "The current status or asking price for the domain sale"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 21/24
- Content legibility: 20/26
- Discovery surface: 0/20
- Identity & policy: 0/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No discoverable sitemap
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] No API or feed to read
- [blocker] No MCP endpoint to call

## FAQ
Q: Is Weflair readable by AI agents?
A: Weflair (weflair.com) scores 49 out of 100 for agent readiness, grade D, measured 1 week ago, on 23.09.2026. 0 of 3 agent classes we test can use the site, and 5 checks currently block agents outright.

Q: What stops agents from using weflair.com?
A: The heaviest problems are: No discoverable sitemap; No llms.txt; The site does not say who it is; No API or feed to read; No MCP endpoint to call. 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 Weflair agent-readiness score calculated?
A: Qomvia fetches public pages of weflair.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.

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 1 week ago, on 23.09.2026.

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