Aloha Digital

Is Your Site Agent-Ready?

Scan any URL against 20 emerging agent-readiness standards — from robots.txt and Markdown negotiation to MCP, OAuth discovery, Agent Skills, WebMCP, and agentic commerce. Open methodology. Paste-ready fix prompts.

Scans take 10–25 seconds · Results are public · Free

Experiment20 probes · Methodology in fluxRead the disclaimer →
What you get back

A scorecard your devs can act on.

Twenty probes, scored deterministically. Each one tagged by adoption flag, so your team knows what's table-stakes and what's still on the horizon.

lexity.ai

Scanned just now · 20 probes · 0.18s

Complete
4of 14

4 pass · 10 fail

  • Discoverability
    3/4
  • Content negotiation
    0/1
  • Bot access control
    0/2
  • API · Auth · MCP
    1/7
  • Agent commerce
    0/0
robots.txt· Discoverability
High adoption
EvidencePlain EnglishFix itrobots.txt found and contains directives

Request

GEThttps://lexity.ai/robots.txt

Response

200OK·text/plain; charset=utf-8·103 B·66 ms

Response headers

  • content-type:text/plain; charset=utf-8
  • content-length:103
  • cache-control:public, max-age=0, must-revalidate
  • access-control-allow-origin:*

Body excerpt

/robots.txt · 4 lines
User-Agent: *
Allow: /
Disallow: /api/

Host: https://lexity.ai
Sitemap: https://lexity.ai/sitemap.xml

robots.txt is a plain-text file at the root of your domain that tells automated visitors which parts of your site they may read. Missing it means well-behaved bots usually treat everything as crawlable — and you lose the chance to record any preference. RFC 9309 ↗

ProbeAdoptionStatus
  • robots.txt
    High adoption
  • Sitemap
    High adoption
  • JSON-LD structured data
    High adoption
  • Link headers (RFC 8288)
    Real & growing
  • llms.txt (Chrome Lighthouse)
    Early but real
  • Markdown Negotiation
    Early but real
+14more checks·run a scan to see them all
Adoption flags:High adoptionReal & growingEarly but realSpeculativeAloha ext.
Read before you ship

Half of these standards are still being argued.

Use this scan as a starting point, not a spec sheet. Every check links back to the canonical source so your team can validate before implementing.

Adoption flags, explained

Every check is tagged with one. Use it to decide what to ship now vs. what to watch.

  • High adoption

    Established standard, widely supported across major crawlers and platforms. Safe to implement; reasonable to expect bots to honour.

  • Real & growing

    Published spec or near-final RFC with verified production use at multiple platforms. Stable enough to ship.

  • Early but real

    Active spec work or first-mover production implementations. Worth shipping if you're an early adopter, but expect the surface to shift.

  • Speculative

    Proposed standard, working draft, or competing approaches. Worth watching, but assume breaking changes before it stabilises.

  • Aloha extension

    A check we run that is not yet a published standard. Useful operational signal — not authoritative.

What we based these checks on

Every probe links to a canonical source. The biggest ones live here.

This scanner is an experiment. Validate before you implement.

We built this to learn alongside the agentic-web stack — many of the standards we probe are early, still under spec work, or contested between vendors. Before implementing anything beyond robots.txt and JSON-LD: read the canonical spec we link, confirm the standard hasn't shifted since this scan, and consult a technical SEO or platform expert for critical surfaces. The checks themselves will evolve as the ecosystem does. This is open methodology — not legal, security, or compliance advice.

How it works

No black-box scoring. Just probes you can rerun in your terminal.

We built the scanner the way the spec authors meant the standards to be tested — every probe deterministic, every result reproducible.

  1. 01

    Deterministic HTTP probes

    Every finding is a request you can reproduce in your terminal with curl. No AI in the scoring loop, no proprietary signals — just request, response, body excerpt.

  2. 02

    Honest adoption flags

    Each check carries a flag — high adoption, real-and-growing, early-but-real, speculative, or Aloha-extension — so your team knows what to ship now vs. what to watch.

  3. 03

    Paste-ready fix prompts

    For every fail, we generate a ready-to-paste prompt for Claude Code or Cursor. Your devs go from "what is x402" to a merged PR without reading a spec.

A scanner built for the agentic web — not retrofitted for it.

  • 20

    Deterministic probes

  • 5

    Categories of agent readiness

  • < 25s

    From URL to full report

  • 0

    AI in the scoring loop

Take it with you

Hand the full audit to your devs.

Every scan exports as a single Markdown file — request, response, body excerpt, and a plain-English explainer for each check. Paste it into Claude Code, Cursor, or your project tracker.

Want a hand interpreting the results? Talk to us →