# Fruityllama (fruityllama.co.uk): agent-readiness 58/100, grade D

> Rank 470 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T04:10:15.933Z. Page: https://qomvia.com/site/fruityllama-co-uk  JSON: https://qomvia.com/api/score/fruityllama-co-uk

## Summary

{
  "known": false,
  "confidence": null,
  "summary": null,
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "I have no specific information about fruityllama.co.uk from my training data.",
    "I cannot provide details on its services, target audience, or operational geography.",
    "Its market reputation, client success stories, or business performance are unknown to me.",
    "I cannot identify direct competitors or alternatives based on my knowledge.",
    "I have no data on its history, strengths, or unique selling propositions."
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 21/26
- Discovery surface: 5/20
- Identity & policy: 3/12
- Agent-facing performance: 5/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

## FAQ
Q: Is Fruityllama readable by AI agents?
A: Fruityllama (fruityllama.co.uk) scores 58 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 fruityllama.co.uk?
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 Fruityllama agent-readiness score calculated?
A: Qomvia fetches public pages of fruityllama.co.uk 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/