# Lsstudio (lsstudio.co): agent-readiness 47/100, grade D

> Rank 756 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T20:50:16.835Z. Page: https://qomvia.com/site/lsstudio-co  JSON: https://qomvia.com/api/score/lsstudio-co

## Summary

{
  "known": false,
  "confidence": "high",
  "summary": "I do not have specific pre-existing knowledge about lsstudio.co from my training data.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific business model and services offered by lsstudio.co",
    "Its target audience and geographical reach",
    "Its market position and main competitors",
    "Its unique selling propositions or notable features",
    "Any recent news, updates, or user reviews related to the site"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 21/24
- Content legibility: 11/26
- Discovery surface: 7/20
- Identity & policy: 0/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] The site does not say who it is
- [blocker] No API or feed to read
- [blocker] No MCP endpoint to call
- [improvement] Title, description and canonical URL
- [improvement] No stated policy for automated access

## FAQ
Q: Is Lsstudio readable by AI agents?
A: Lsstudio (lsstudio.co) scores 47 out of 100 for agent readiness, grade D, 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 lsstudio.co?
A: The heaviest problems are: The site does not say who it is; No API or feed to read; No MCP endpoint to call; Title, description and canonical URL; 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 Lsstudio agent-readiness score calculated?
A: Qomvia fetches public pages of lsstudio.co 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 yesterday, on 29.09.2026.

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