# Kexino (kexino.com): agent-readiness 78/100, grade B

> Rank 21 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T02:10:15.884Z. Page: https://qomvia.com/site/kexino-com  JSON: https://qomvia.com/api/score/kexino-com

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not possess specific, distinct knowledge about Kexino.com from my training data. Therefore, I cannot provide a detailed summary of its operations or services based on pre-existing information.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "specific client base and typical project scope",
    "geographic operational focus and main market presence",
    "unique selling propositions or core methodologies",
    "employee count and internal organizational structure",
    "founding date and history of the business"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 24/26
- Discovery surface: 12/20
- Identity & policy: 8/12
- Agent-facing performance: 8/8
- Agent protocols: 2/10
Failing checks:
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No Content Signals
- [improvement] Machine-readable data surface
- [improvement] No Markdown for agents

## FAQ
Q: Is Kexino readable by AI agents?
A: Kexino (kexino.com) scores 78 out of 100 for agent readiness, grade B, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 1 check currently block agents outright.

Q: What stops agents from using kexino.com?
A: The heaviest problems are: No MCP endpoint to call; No stated policy for automated access; No Content Signals; Machine-readable data surface; No Markdown for agents. 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 Kexino agent-readiness score calculated?
A: Qomvia fetches public pages of kexino.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 today, on 30.09.2026.

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