# Sea (sea.fr): agent-readiness 52/100, grade D

> Rank 660 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T22:00:16.502Z. Page: https://qomvia.com/site/sea-fr  JSON: https://qomvia.com/api/score/sea-fr

## Summary
Category: Manufacturing and industrial
{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, pre-existing knowledge about the website sea.fr. My training data does not contain enough information to confidently describe it.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific products and services offered by sea.fr.",
    "Its primary target audience or customer base.",
    "Its geographic areas of operation.",
    "Its market position and competitive landscape.",
    "Any unique selling propositions or notable features."
  ],
  "alternatives": [],
  "business": "I do not have specific, pre-existing knowledge about the business conducted by sea.fr.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 18/26
- Discovery surface: 5/20
- Identity & policy: 0/12
- Agent-facing performance: 5/8
- Agent protocols: 0/10
Failing checks:
- [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
- [improvement] No stated policy for automated access

## FAQ
Q: Is Sea readable by AI agents?
A: Sea (sea.fr) scores 52 out of 100 for agent readiness, grade D, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright.

Q: What stops agents from using sea.fr?
A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; No MCP endpoint to call; No stated policy for automated access. 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 Sea agent-readiness score calculated?
A: Qomvia fetches public pages of sea.fr 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 — category ranking: https://qomvia.com/leaderboard/manufacturing-industrial
- Score another site: https://qomvia.com/