# 33degres (33degres.com): agent-readiness 37/100, grade F

> Rank 851 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T17:50:45.233Z. Page: https://qomvia.com/site/33degres-com  JSON: https://qomvia.com/api/score/33degres-com

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific prior knowledge about 33degres.com. Its self-description indicates it provides scenic design and modeling services, making creators' ideas tangible, and also offers related training.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific client projects or portfolio details",
    "Actual market reputation and client satisfaction",
    "Pricing structure for services or training programs",
    "Precise geographic areas of operation beyond French language indication",
    "Overall business size and operational capacity"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 19/24
- Content legibility: 8/26
- Discovery surface: 0/20
- Identity & policy: 2/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 33degres readable by AI agents?
A: 33degres (33degres.com) scores 37 out of 100 for agent readiness, grade F, measured 2 days ago, on 28.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 33degres.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 33degres agent-readiness score calculated?
A: Qomvia fetches public pages of 33degres.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 2 days ago, on 28.09.2026.

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