Agent-readiness report
Is Axpel-oneforall agent-ready?
No class of agent can use Axpel-oneforall today: they cannot call it as a tool.
axpel-oneforall.ch, last scanned 3 days ago, on 27.09.2026
Agent classes working
0/3
Score history
▲ 34 scans since 20.09.2026
- 3
- Blocking agents
- 13
- Weak spots
- 10/26
- Checks passed
What costs Axpel-oneforall the most
0 of 3 agent classes work
- !Answer engines & research agents
- ✕MCP tool-callers
- !Summarisers & knowledge agents
- ✕
No llms.txt
Nothing tells an agent where the useful pages, feeds and policies are.
Blocker - ✕
No API or feed to read
Every integration has to scrape HTML, which most integrators will not do.
Blocker - ✕
No MCP endpoint to call
Tool-calling assistants have no function to call, so they can only scrape.
Blocker - ✕
No stated policy for automated access
Cautious platforms will not act on the site without an explicit permission signal.
Improvement - ✕
No machine-readable contact
When something breaks, an agent operator has no documented way to reach you.
Improvement
✓10 checks passed · 11 more to fix+−
Free dashboard
Track axpel-oneforall.ch and watch it climb.
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
- 16 optimization suggestions, ready today
- Weekly re-scan with alerts on every change
- Rank and rival moves in one view
Your dashboard
We email you a sign-in link and add axpel-oneforall.ch to your dashboard.
- Re-scan weekly
- Fixes listed
- Rivals tracked
Check a rival
5 domains free, unlimited with a plan.
Machine interfaces
Axpel-oneforall exposes 3 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, Server-rendered content.
Locked
All 8 interfaces and 26 checks for axpel-oneforall.ch
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsE-commerce & product feeds
Measured separately, not part of the public score or rank
Add-on score
49/100
- 5
- Blocking agents
- 3
- Weak spots
- 4/12
- Checks passed
- ✕
Not on Qomvia Market
Agents using Qomvia cannot get an agent price or a payable order from this shop.
- ✕
No reachable cart URL
An agent cannot hand a filled basket back to the shopper.
- ✕
No product feed for agents to ingest
Agent platforms cannot load the catalogue in one request, so coverage stays partial.
- ✕
Agents cannot check out
ChatGPT can mention the shop but has to hand the shopper off instead of buying.
- ✕Autonomous shopping agents
- ✕Feed & API integrators
- !Price-comparison & monitoring bots
- ✕Agent payment protocols
- ✓Catalogue access100%
- !Product data legibility77%
- ✕Agent-commerce protocols0%
- !Checkout traversability43%
The seal
Agent-Readable
Agents can read the site, but acting on it still breaks. Paste this line where you want the seal: it is drawn at runtime, so it upgrades itself when you improve and removes itself if a deploy closes the site to agents.
<script src="https://qomvia.com/badge.js" data-slug="axpel-oneforall-ch" async></script>There is no image URL and no static version. The seal exists only as markup we serve per request, which is what makes it worth displaying.
- Agent-Ready Champion90+
- Agent-Ready75+
- Agent-Readable60+
- In Progress40+, dashboard only
Axpel-oneforall and AI agents: common questions
Is Axpel-oneforall readable by AI agents?+−
Axpel-oneforall (axpel-oneforall.ch) scores 60 out of 100 for agent readiness, grade C, measured 3 days ago, on 27.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright.
What stops agents from using axpel-oneforall.ch?+−
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.
How is the Axpel-oneforall agent-readiness score calculated?+−
Qomvia fetches public pages of axpel-oneforall.ch 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. E-commerce & product feeds checks are scored separately (49/100) and do not affect the public score or rank.
How often is this score updated?+−
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 3 days ago, on 27.09.2026.
Compare and keep reading
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.