What was implemented — agent readiness only
All verified at isitagentready.com/belmon.tech — 25 Aug 2026, level 4 Agent-Integrated. Only what the scan validates; no invention.
| Area | Spec | Estado |
|---|---|---|
| robots.txt | AR-DISC-01 | pass — route handler + Content-Signal |
| sitemap.xml | AR-DISC-02 | pass — vía robots.txt Sitemap: |
| Link headers | AR-DISC-05 | pass — api-catalog + describedby (llms.txt) |
| Markdown for Agents | AR-CONT-02 | pass — proxy.ts Accept: text/markdown |
| Content-Signal | AR-DISC-01 | pass — ai-train=no, search=yes |
| Agent Skills | AR-CAPA-07 | pass — /.well-known/agent-skills/ |
| DNS-AID | DNS-AID | fail — no configurado (fuera del repo, Cloudflare) |
| API Catalog | AR-IDEN-06 | fail — falta linkset RFC 9264 |
| MCP / A2A | AR-CAPA-01/04 | n/a — sin superficie MCP/A2A |
Measurement — isitagentready
| Check | Status | Source |
|---|---|---|
| Level | 4 — Agent-Integrated | isitagentready.com/belmon.tech — 25 ago 2026 |
| Discoverability | 3 pass / 1 fail (DNS-AID) | robotsTxt, sitemap, linkHeaders pass |
| Bot Access Control | 2 pass | contentSignals + ai bot rules |
| Protocol Discovery | 1 pass (Agent Skills) | apiCatalog fail (linkset), resto n/a |
Commerce neutral (not a shop). See full report at the link above — no invented citation metrics.
Limitations
The domain registrar doesn't allow creating the SVCB/HTTPS record types required by DNS-AID (_index._agents, _a2a._agents, _mcp._agents). We tried delegating the _agents zone to Cloudflare and migrating the whole DNS, but the registrar doesn't expose those types in its panel and rejects them via AXFR/DoH. Until the registrar supports them or the domain is moved, DNS-AID will remain fail — documented here as a known limitation, not an implementation bug.