# Minnesota (minnesota.agency): agent-readiness 49/100, grade D

> Rank 717 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T12:20:16.234Z. Page: https://qomvia.com/site/minnesota-agency  JSON: https://qomvia.com/api/score/minnesota-agency

## Summary
Category: IT services and agencies
{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific pre-existing knowledge about the website minnesota.agency as a distinct business entity.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific services or products offered by minnesota.agency.",
    "The target audience or customer base of minnesota.agency.",
    "The primary geographic market or operational areas of minnesota.agency.",
    "Any unique strengths or differentiating factors of minnesota.agency.",
    "Direct competitors for minnesota.agency."
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 22/24
- Content legibility: 19/26
- Discovery surface: 3/20
- Identity & policy: 2/12
- Agent-facing performance: 3/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] Server responds too slowly for agents
- [blocker] No MCP endpoint to call

## FAQ
Q: Is Minnesota readable by AI agents?
A: Minnesota (minnesota.agency) scores 49 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 5 checks currently block agents outright.

Q: What stops agents from using minnesota.agency?
A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; Server responds too slowly for agents; 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 Minnesota agent-readiness score calculated?
A: Qomvia fetches public pages of minnesota.agency 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/it-services
- Score another site: https://qomvia.com/